[gatein-issues] [JBoss JIRA] Closed: (GTNPORTAL-1407) Language doesn't persist when session timeout

[Marko Strukelj (JIRA)]

     [ https://jira.jboss.org/browse/GTNPORTAL-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marko Strukelj closed GTNPORTAL-1407.
-------------------------------------

    Resolution: Done


This fix was broken again for a while, as I disabled cookies support while working on GTNPORTAL-1306.
I added the cookie support back so it's again fixed.

> Language doesn't persist when session timeout
> ---------------------------------------------
>
>                 Key: GTNPORTAL-1407
>                 URL: https://jira.jboss.org/browse/GTNPORTAL-1407
>             Project: GateIn Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Internationalization and Localization
>    Affects Versions: 3.1.0-GA
>         Environment: all
>            Reporter: Benjamin Paillereau
>            Assignee: Marko Strukelj
>            Priority: Critical
>             Fix For: 3.2.0-GA
>
>
> There is a critical issue in GateIn about i18n. In public mode, the current portal language user choice is stored in the session. If the user waits the session timeout then we lose the language and go back to the default one.
> If you take WCM for example, for performance reasons, we reduce automatically the session MaxInactiveInterval to 60sec.
> So, if you change the language in public mode, you lose it after 60 sec if you don't refresh your page.
> We can see a workaround and a longterm solution.
> Workaround : use a cookie and store the language in a cookie. When we load the page, if the current language is different than the one in the cookie, we will prefer the cookie.
> Longterm solution : we must have a unique url for each language/page.
> http://mysite.com/portal/public/website/mypage => default language
> http://mysite.com/portal/fr/public/website/mypage => fr language
> or
> http://mysite.com/portal/fr/website/mypage => fr language
> URL format is still to be determined but the point is to have a unique url. The best solution should be to be able to choose the url format in the UI when creating a website.
> Using unique urls also allows to use a web cache (like varnish), which is not possible now.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira