[Building Sakai] Tool must be available but not in the left navigation area

Steve Swinsburg steve.swinsburg at gmail.com
Sat Aug 29 02:31:02 PDT 2009


If its just for the maintain role, just use the PageOrder tool in Site  
Info to hide it. That works from the set of permissions available for  
maintain only (site.upd I think?). That way the tool is available for  
other users via a direct URL as well.

However, the key role of the 'functions.require' method to is that a  
tool disappears if a user lacks the appropriate permission. So, you  
could create a super simple service that just registers some new  
functions, add them to the roles you want, set the property for the  
tool and you are done.

ie add this to the tool reg file:
<configuration name="functions.require" value="some.function" />
cheers,
Steve


On 28/08/2009, at 2:00 AM, John Bush wrote:

> This sounds like something you could easily do if you use the xsl- 
> portal if you are ok with essentially hard coding the rules in your  
> xsl.  The xsl-portal supports loading the portal.xslt out of any  
> skin directory.  So that gives you pretty good control over  
> everything the portal does without having to modify any code.
>
> John Bush
> Development Manager
> rSmart
>
>
>
>
> On Aug 26, 2009, at 5:04 AM, Frank Benneker wrote:
>
>> Thx fot the suggestions.
>>
>> I think only the first one will work in practice because I want to  
>> have the link in the menubar available for the role: maintain
>>
>> I think it will be a new requirement use case:  the option to make  
>> items in the menubar visible or not based on the role in the site.
>> The tool itself should be available for all roles.
>>
>> Frank
>>
>> Op 26 aug 2009, om 11:23 heeft Roland Groen het volgende geschreven:
>>
>>> Hiding tools using functions.require will never work, because  
>>> first you deny access and than require it. Getting that to work  
>>> will be a bug and should be reported as such ;-)
>>>
>>> I can think of 2 solutions:
>>>
>>> 1) Change code, To hide the code in the menu a property could be  
>>> set in the page and the portal rendering code could pick up that  
>>> property in order not to render the item. This will require  
>>> changes in the rendering code and will also introduce some porting  
>>> issues towards future versions.
>>>
>>> 2) Use the skin css to hide the tool in the menubar. Each tool has  
>>> it's own css class, the next piece of css will at least get rid of  
>>> the link:
>>>
>>> a.icon-sakai-rwiki {
>>>   display: none;
>>> }
>>>
>>> This will hide all wiki tool pages, also for the teachers.
>>>
>>> --
>>> Roland.
>>>
>>>
>>
>> _______________________________________________
>> 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"
>
> _______________________________________________
> 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/20090829/8654a19e/attachment.html 


More information about the sakai-dev mailing list