[Building Sakai] Installing Australe 2.7.0.x on Sakai 2.7.1

Steve Swinsburg steve.swinsburg at gmail.com
Tue Sep 21 04:25:03 PDT 2010 

Hi Warwick,

I haven't modified the web service. Disallowing all functions and just using the ones from the template would be too drastic, as some tools allow site maintainers to customise the permissions on a per site basis, so these mods would be lost. So at the moment it just adds new permissions from the template and won't remove any. A future modification might allow the removal.

cheers,
Steve


On 21/09/2010, at 6:21 PM, Warwick Chapman wrote:

> Steve
> 
> Running 2.7.1, I have no realms configured with the melete.student permission and I have configured it only in !site.helper.  I only have two roles in use at the moment, "access" and "maintain" and I'm just adding the "melete.student" and "melete.author" permissions to them respectively.
> 
> Since they are the default roles and existed when the project sites were created, using !site.helper seems to work without changing !site.template or creating a !site.template.project (though it would seem this is good practice and I should get it done).
> 
> I appreciate your post about copyRole and note your comment that it is available by default in 2.7.  Did you end up changing the code to ensure "that the permissions in the target role should all be zapped (ie toRole.disallowAll()) then only get the ones from the template role"?
> 
> -- Warwick Bruce Chapman | +27 83 7797 094 | http://warwickchapman.com
> 
> 
> On Tue, Sep 21, 2010 at 8:34 AM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> The !site.helper realm allows you to specify additional permissions for roles. But it's an all or nothing setup, so individual sites won't be able to have customised permissions that include that permission.
> 
> Plus, you need that role in those sites for it to match up, ie if you don't have the access role in a site, it won't work. You are best setting up your roles in something like !site.template then synchronising the permissions across the sites.
> 
> I wrote an article about it:
> http://steve-on-sakai.blogspot.com/2009/05/roles-in-sakai-sites.html
> 
> cheers,
> Steve
> 
> 
> 
> On 21/09/2010, at 4:20 PM, Warwick Chapman wrote:
> 
>> Ok, so if I create a role called "access" in !site.helper and tick melete.student, it works.  Is there any reason why I should not use !site.helper instead of worrying about individual realms like !site.template.course?
>> 
>> -- Warwick Bruce Chapman | +27 83 7797 094 | http://warwickchapman.com
>> 
>> 
>> On Tue, Sep 21, 2010 at 8:01 AM, Warwick Chapman <warwickchapman at gmail.com> wrote:
>> Rashmi
>> 
>> Thank you.
>> 
>> !site.template.course is now configured as you requested.  My Melete content is in a project site and I do no have a !site.template.project as alluded to in your instructions.  Will the project sites then use !site.template.course instead or should the same settings be configured in !site.template?
>> 
>> 
>> -- Warwick Bruce Chapman | +27 83 7797 094 | http://warwickchapman.com
>> 
>> 
>> On Mon, Sep 20, 2010 at 10:37 PM, Rashmi Maheshwari <rashmi at etudes.org> wrote:
>> Our upcoming release is 2.8. 
>> 
>> For the roles, check the installation steps. 
>> Attaching the same here. 
>> 
>> 8) Update Sakai Roles for Melete
>> 
>> Update Sakai Roles (under realms) to include Melete permissions to your roles. If you are upgrading Melete in your Sakai instance, no roles changes are needed.
>> 
>> Log on as Sakai admin.
>> Check appropriate Melete permissions under the roles in !site.template.course.
>> 
>> Check melete.author for instructor, teaching assistant types of roles (maintain) to which you want to give 'authoring / manage' rights.
>>  
>> 
>> Check melete.student for student types of custom roles that you have (access) to which you want to give 'viewing' rights.
>> 
>> If you have project sites and related roles in !site.template.project, appropriate permissions (melete.student or melete.author) need to be checked as defined above, based on what rights you want to give to the roles.
>> 
>> CAUTION:
>> 
>> a. IF YOU FAIL TO CHECK THE MELETE.STUDENT AND MELETE.AUTHOR PERMISSIONS FOR YOUR ROLES, MELETE WILL NOT WORK PROPERLY.
>> 
>> b. IF YOU ADD MELETE TO _EXISTING SITES_, USERS WILL NOT HAVE THE MELETE PERMISSIONS THAT YOU CHECKED. YOU WILL NEED TO USE !SITE.HELPER OR OTHER SCRIPT TO PROPAGATE THE MELETE PERMISSION TO EXISTING SITES.
>> 
>> 
>> 
>> Hope this helps,
>> Rashmi
>> 
>> 
>> Warwick Chapman wrote:
>>> 
>>> J-F
>>> 
>>> I tried your code change and it no longer crashes but I still do no see any content in Melete, just the Table of Contents and the headings.
>>> 
>>> Rashmi, what version is your upcoming release? 2.7.3?  How do I assign a user a melete.student role?  I was able to author the content without assigning anyone a melete.author role?
>>> 
>>> I'm a little confused by the 2 melete roles...
>>> 
>>> -- Warwick Bruce Chapman | +27 83 7797 094 | http://warwickchapman.com
>>> 
>>> 
>>> On Mon, Sep 20, 2010 at 10:07 PM, Rashmi Maheshwari <rashmi at etudes.org> wrote:
>>> Hi Warwick Chapman and Jean-Francois, 
>>> Melete has defined its own 2 roles - melete.author (basically with maintain role and we call this person as INSTRUCTOR) and melete.student (access role and similarly we call this person STUDENT). We have fixed this issue in our upcoming release. Take a look at rev 69255 and rev 69283. 
>>> 
>>> thanks,
>>> Rashmi
>>> 
>>> =================================
>>> Here are rev details. These revisions apply changes to few new classes and methods, so be very careful if you are planning to apply the patch.
>>> 
>>> 
>>> Revision: 69255
>>> Author: mallika at etudes.org
>>> Date: 4:48:27 PM, Thursday, July 15, 2010
>>> Message:
>>> Fix for ME-1249, this fix replaces sessionmap.get(role) with calls to meletesecurityservice. It consolidates student instructor view calls to listviewAction, removes student preview image from what's next page, does the role check at db level for getnextseq and getprevseq, removes some unnecessary code with sequence numbers at the bean layer.
>>> ----
>>> Modified : /etudes/melete/trunk/melete-api/src/java/org/etudes/api/app/melete/ModuleService.java
>>> Modified : /etudes/melete/trunk/melete-app/src/java/org/etudes/tool/melete/BookmarkPage.java
>>> Modified : /etudes/melete/trunk/melete-app/src/java/org/etudes/tool/melete/ListModulesPage.java
>>> Modified : /etudes/melete/trunk/melete-app/src/java/org/etudes/tool/melete/MeleteSiteAndUserInfo.java
>>> Modified : /etudes/melete/trunk/melete-app/src/java/org/etudes/tool/melete/NavPage.java
>>> Modified : /etudes/melete/trunk/melete-app/src/java/org/etudes/tool/melete/ViewModulesPage.java
>>> Modified : /etudes/melete/trunk/melete-app/src/java/org/etudes/tool/melete/ViewNextStepsPage.java
>>> Modified : /etudes/melete/trunk/melete-app/src/java/org/etudes/tool/melete/ViewSectionsPage.java
>>> Modified : /etudes/melete/trunk/melete-app/src/webapp/WEB-INF/faces-config.xml
>>> Modified : /etudes/melete/trunk/melete-app/src/webapp/melete/view_whats_next.jsp
>>> Modified : /etudes/melete/trunk/melete-impl/src/java/org/etudes/component/app/melete/ModuleDB.java
>>> Modified : /etudes/melete/trunk/melete-impl/src/java/org/etudes/component/app/melete/ModuleServiceImpl.java
>>> 
>>> Revision: 69283
>>> Author: mallika at etudes.org
>>> Date: 2:16:45 PM, Monday, July 19, 2010
>>> Message:
>>> Fix for ME-1249, removing isauthor and isstudent check from constructor. Removing import statement for facesmessage from viewmodulespage as it is not needed
>>> ----
>>> Modified : /etudes/melete/trunk/melete-app/src/java/org/etudes/tool/melete/ListModulesPage.java
>>> Modified : /etudes/melete/trunk/melete-app/src/java/org/etudes/tool/melete/ViewModulesPage.java
>>> 
>>> ==========================
>>> 
>>> 
>>> 
>>> 
>>> Warwick Chapman wrote:
>>>> J-F
>>>> 
>>>> As per the attached image, the role is "access".
>>>> 
>>>> Is that right?
>>>> 
>>>> -- Warwick Bruce Chapman | +27 83 7797 094 | http://warwickchapman.com
>>>> 
>>>> 
>>>> On Mon, Sep 20, 2010 at 4:34 PM, Jean-Francois Leveque <jean-francois.leveque at upmc.fr> wrote:
>>>> Is seems role is null on line 67 of melete/melete-app/src/java/org/etudes/tool/melete/NavPage.java.
>>>> 
>>>> Looks like this part of the code should be made more resilient.
>>>> 
>>>> Please try to replace
>>>> if (role.equals("INSTRUCTOR"))
>>>> with
>>>> if ("INSTRUCTOR".equals(role))
>>>> 
>>>> It nonetheless seems your unprivileged user has no role, which could be a important problem.
>>>> 
>>>> 
>>>> Cheers,
>>>> 
>>>> J-F
>>>> 
>>>> 
>>>> <Mail Attachment.jpeg>
>>> 
>>> 
>>> -- 
>>> Rashmi Maheshwari
>>> Learning Systems Developer
>>> Etudes Inc
>>> http://etudes.org
>>> 
>> 
>> 
>> -- 
>> Rashmi Maheshwari
>> Learning Systems Developer
>> Etudes Inc
>> http://etudes.org
>> 
>> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20100921/199b7b46/attachment.html

More information about the sakai-dev mailing list