Worksites need to support locale preferences
Description
Attachments
depends on
is duplicated by
is related to
Activity
Daniel Merino October 30, 2012 at 3:57 AM
This feature doesn't work with .anon role access. If you enter a public site, tools are shown with Tomcat's default language. I have confirmed this in trunk.
Hudson CI Server April 8, 2011 at 10:09 PM
Integrated in sakai trunk #488 (See http://builds.sakaiproject.org:8080/job/sakai%20trunk/488/)
Worksites need to support locale preferences
Worksites need to support locale preferences
Bryan Holladay April 7, 2011 at 5:16 AM
r91427 portal
r91428 site-manage
This is resolved in trunk
Alan Regan April 6, 2011 at 12:02 PMEdited
This is a feature request and needs to be added as a core feature in 2.7, 2.8, etc. Specifically, there needs to be a mechanism in Site Info where an instructor (course site) or the maintain role (project site) can specify the default language for the site. For example, in the "Manage Access" or "Site Information" area, perhaps a "Site Language" option is available. This selection needs to override any user-specified language preference. As stated in the description, this is critical for language instruction courses. Professors need to immerse the student completely in the language, and this feature would help faculty members encourage foreign language mastery.
I can also see where an institution that automatically generates course sites might want to administratively assign a default language based on course subject or subject and number, such as FRE, SPAN, GER, JAP, CHIN; or FRE 4xx, ITAL 6xx, etc. This way, the institution could save professors an additional click. (The more clicks we save, the easier the system and the greater the user satisfaction.)
Can we update the Affected Versions for this JIRA ticket to 2.7, 2.8, and 2.9?
Can we add the Site Info tool as a component for this ticket?
Miguel Pellicer November 10, 2010 at 11:59 PM
This patch works in 2.7.1
Worksites (especially course-sites) need to support a language/locale preference that trumps the language/locale of the user and of the system. Specific application for this include language-based courses.
Suggested implementation:
Set new SAKAI_SITE_PROPERTY flag: org.sakaiproject.site.LOCK_LOCALE = [locale-identifier]
The LOCK_LOCALE property could be set in the Worksite Setup tool using a checkbox. If set, the locked locale would be equal to the user's current language/locale preference.