 |
History
| Log In
|
|
|
|
I linked
A customer is willing to propagate the locale chosen by a user in public mode to the private mode. This makes things a bit more complicated. For users who allow cookies, can we leverage them and try something like this (before something more complete is implemented ;-) ): - Choice in the preferences have a higher priority than choice in the cookies, which have a higher priority than browser choice, which have a higher priority than default portal locale. - Choosing "default language" deletes the cookie and/or user preferences. We have a confict in login of language. This is the situation
1. in public mode, user change language setting to -> france for example, portal will change language to france 2. if user login and this user have user language preference is vietnamese 2.1 -> from 2.2 -> keep user language preference (vietnamese) or private mode What we can do for this problem?. To solve this : as soon as the user logs in, switch to his preferred user locale.
I've resolved this issue by above priority, but now I put user language preference in user profile, so that we can't pre-configure language for default user of portal such as root, john...
To set user language preference we can go to edit use or change language of private mode for existed user. I'll improve this issue to pre-configure language for default user as soon as posible. Patrice, if you have any request, please let me know. Many thanks. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Resolved
Critical
language as a user preference
- Look for user preference, if it doesn't exist (first login for example) or not supported by portal, then
- Look for browser preferred locale (in http headers). If not found or not supported by portal, then
- Take portal default locale.
Beware to use Locale instead of simply language. Date formats should change with locale.
The user locale should be easily available to other portql applications (REST API?) that want to localize their UI