[#SAK-10244] Allow sakai.properties setting to control which tools are allowed to have multiple placements in a site

Sakai

Allow sakai.properties setting to control which tools are allowed to have multiple placements in a site

Created: 30-May-2007 16:23 Updated: 27-Oct-2009 13:45

Component/s:

PageOrderHelper, Worksite Setup

Affects Version/s:

2.4.0

Fix Version/s:

2.6.0

Time Tracking:

Not Specified

Issue Links:

Depend

This issue is depended on by:

RSV-7 Ability to have more than one instance of Resources Viewer per site

2.6.x Status:	None
2.5.x Status:	None
2.4.x Status:	None

Description

« Hide

Currently the tools that normal users can add to a site more then once are hard coded into SiteAction.java and into the page order helper. This really should not be the case. System adminstrators should be able to control which of the tools that they have installed are allowed multiple placements in a site.

I propose we have a sakai.properties setting that takes a list of tool Ids and all tool ids listed are allowed multiple placements in a site.

All

Comments

Work Log

Change History

Subversion Commits

git Commits

Sort Order:

[ Permlink | « Hide ]

Stephen Marquard added a comment - 01-Jun-2007 02:29

It might be preferable to define this in the tool registration file, or perhaps set defaults there which can be overridden in sakai.properties.

In the case of a new tool, one ideally doesn't want to have to get either the system-wide sakai.properties defaults or the local instance's sakai.properties updated for the tool to behave correctly (i.e. its initial configuration should be self-contained).

[ Permlink | « Hide ]

Joshua Ryan added a comment - 01-Jun-2007 11:22

Having the defaults in the tool definitions and override from sakai.properties sounds like a good plan.

How about:
<configuration name="allowMultiple" value="true" />

[ Permlink | « Hide ]

John Leasia added a comment - 27-Jun-2007 07:19

changing back the tag changes I just made - not sure this should be in 2.4.x

[ Permlink | « Hide ]

Joshua Ryan added a comment - 26-Oct-2007 08:26

I ended up with a tool configuration of "<configuration name="allowMultiple" value="true" />" that allows a tool to be a multiplacement tool plus at the system level in sakai.properties you can set "sakai.site.multiPlacementTools" to a list of tool ids that you want to be allowed to be multiplacement tools. Currently these two setting add to each other, so if a tool defines itself as allowMultiple==true in it's tool def it will be a multiplacement tool no matter what you have in sakai.site.multiPlacementTools. I'm open to discussion if you feel the sakai.properties setting should over write the other instead.