|
Rita Pavolka adds "As long as we're talking about Preferences, could you consider reordering the content for the "Notifications" page. Like the "Sesame Street, which of these things is not like the other game" when creating support documents it would make it easier to separate the "Email Archive" notifications from the others. Placing it first or last would do that. See attached jpg." So please also move the email notification control to the top, above the Announcement notification section.
The idea of customization of preference action tabs in sakai.properties has been implemented and committed at https://source.sakaiproject.org/svn/ctools/trunk/user/user-tool-prefs/
Savitha, do you plan to contribute the fix back to Sakai?
Yes, eventually. This is included in the current release of ctools. Depending upon the feed back, we will eventually merge it with sakai.
In the preference tool, the following features have been incorporated and committed in sakai-trunk
-Ability to configure the number and order of the preference tabs in preference.pages in sakai.properties. -The first page will be the first tab configured in the preference.pages. -Resolved a bug -Shifted the email notification option down as specified. - If its not configured in sakai.properties, the default list will be Customize Tabs, Notification, Time Zone, Language. The action tabs can be customized in sakai.properties as follows- # Preference tool Configuration. preference.pages= prefs_tab_title, prefs_noti_title, prefs_timezone_title, prefs_lang_title #Default options-> prefs_tab_title, prefs_noti_title, prefs_timezone_title, prefs_lang_title The preferences have not been re-ordered for the Privacy tab (privacy.jsp) -- which is enabled by setting "enable.privacy.status = true" in sakai.properties. Savitha -- let me know if you need any help with this. Thanks!
sakai/trunk r52109
The reordered links are included in the privacy.jsp page. However, currently the order of "privacy status" link is not configurable, and it just appears as the last link in Preference tool. Should the order of "privacy status" be made configurable as other links? The "Privacy Status", which was configured by enable.privacy.status = true in sakai.properties has been removed.
To enable "Privacy Status", "prefs_privacy_title" has to be included with preference.pages in sakai.properties. This also indicates the order in which the "Privacy Status" link will be displayed with respect to others (Custom Tabs, Notification, Time Zone, Language). e.g., preference.pages= prefs_tab_title, prefs_noti_title, prefs_timezone_title, prefs_lang_title, prefs_privacy_title By Default, if preference.pages is not configured, then the order of links in Preference will be as follows- " Customize Tab, Notification, Time Zone, Language ". Revision- 52140 Need reference's sakai.properties to be updated to explain new settings.
sakai.properties has been updated to include info on the new property
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Task
Closed
Major
Switch default page in Preferences to Customize Tabs
This is to make a sakai property 'preference.pages' that controls which page is seen first in the Preferences tool, and which pages show up at all. The property is set equal to a comma separated list of values identifying the pages (and toolbar actions) which show up. The pages are Notifications, Customize Tabs, Time Zone, Language. The specific values could be the bundle names for the pages. So, something like
preference.pages=prefs_tab_title, prefs_noti_title, prefs_timezone_title, prefs_lang_title
The order of the values in the comma separated list will determine which is the first page and also the order of actions in the toolbar. If a value is missing, that page's action will not show in the toolbar, and so that page will not be reachable via the UI. The first page in the Preferences tool will be the page associated with the first value in the list.
If the preference.pages property is not present, the page order will be the (current) default.
The Preferences tool reset button should take the user back to whatever first page is indicated by preference.pages.
If preference.pages is present, and is set w/o any values, it is ignored. Need to handle (ignore) mispelled/erroneous and empty values in case preference.pages is set with bad values.