Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.7.4
-
Fix Version/s: 2.7.5
-
Component/s: None
-
Labels:None
Description
Using the language switch smarty tag a language switch performed on a page that is only available in a single language, results in a bug that the navigation is still shown in the previous language.
e.g.
- navigate to a page that is only available in german (not english menu exists, not only no english content)
- switch the language to english
- the navigation and the content of the page is still be shown in german, but the language switch displays the german flag, indicating that the language has been changed. But navigating the system still show everything in german, but the language switch still thinks the user langugae is set to english and displays the german flag.
e.g.
- navigate to a page that is only available in german (not english menu exists, not only no english content)
- switch the language to english
- the navigation and the content of the page is still be shown in german, but the language switch displays the german flag, indicating that the language has been changed. But navigating the system still show everything in german, but the language switch still thinks the user langugae is set to english and displays the german flag.
These portlets used the language of the currently active page (if their language configurationwas empty).
The default behaviour was changed, they now use the current session language.
I am not sure whether this is a good idea or not, but it feels better. At the end it depends on the website structure and programming, but most multi-language websites will use the session language switch and not work by e.g. requested items.