Christian Gosch

(Also with this I am afraid I cannot really help in the near future.)

(I do not think that I will be able to work on this the next time because nearly all tests have to be adjusted.)

A proposal is made by https://github.com/finalist/liferay-oidc-plugin/pull/20/commits/6e988f48ba7c56c1f78ca24aff778a777519ee99 . The implementation is located in `LibFilter` and thus should work for both LR62 and DXP. However, if DXP works differently with locale prefixes...

`LocaleUtil.getMostRelevantLocale()` sounds perfect. I did not know about that and will test it. However it must be implemented the same way the logging is implemented. Commit will follow soon referring...

Generally looks promising: ```Java private Locale _getMostRelevantLocale() { Locale locale = LocaleThreadLocal.getThemeDisplayLocale(); if (locale == null) { locale = _getDefault(); } return locale; } ```

Does not work, sorry: On my portal, the default language is `de`. When I use `LocaleUtil.getMostRelevantLocale()`, `en` is used for everything, independent of actually selected portal content language. *But* I...

I have removed all relevant cookies for the tests, and my browser's locale sequence is actually (`de-de`, `de`, `en-us`, `en`) which should result in preferring `de` at least. My OP...

My solution "works for me", but if there is any improvement towards a cleaner solution, I appreciate that :-)

The implementation update now takes the GUEST_LANGUAGE_ID cookie into account. The request´s locale is useless as it seems, but this cookie is used by Liferay to store the last selected...

Hint: After having authenticated, the user´s preferred language seems to be primarily controled by the user profile: After an authenticated user has explicitly chosen a display language, this language will...