Problem Description
Currently, when a user changes the preferred language via the topbar dropdown, the selection is stored primarily as a browser cookie. While this works for the current session and browser, it is not persisted to the user's profile settings in the backend. As a result, if an authorized user switches to a different browser or clears their cookies, their language preference is lost, and they must re-select it manually.
Proposed Enhancement
We want to bridge the gap between the client-side language switcher and the server-side user profile. For authenticated users, the language will be defined in the user’s profile. If a language is set, the top bar language switcher is synchronized with the stored preference. If the user changes the language via the switcher, the change is applied only at the browser level and is not persisted in the database. This is the standard approach followed by similar platforms.
Problem Description
Currently, when a user changes the preferred language via the topbar dropdown, the selection is stored primarily as a browser cookie. While this works for the current session and browser, it is not persisted to the user's profile settings in the backend. As a result, if an authorized user switches to a different browser or clears their cookies, their language preference is lost, and they must re-select it manually.
Proposed Enhancement
We want to bridge the gap between the client-side language switcher and the server-side user profile. For authenticated users, the language will be defined in the user’s profile. If a language is set, the top bar language switcher is synchronized with the stored preference. If the user changes the language via the switcher, the change is applied only at the browser level and is not persisted in the database. This is the standard approach followed by similar platforms.