You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The call to _wdt route triggers a new locale update. If for instance your url schema is /nl/news but your browser is set to 'en_US', the "normal" request will set the locale to 'nl', but the dev route (without locale) will set the locale back to 'en_US', which in case you use a cookie will trigger 2 changes: first the correct 'nl', then the incorrect 'en_US'
The text was updated successfully, but these errors were encountered:
that would probably also affect any ajax calls that have no locale in the url.
but its strange, usually once the locale is determined and in the cookie, it should stick when no locale is explicitly found in the path/domain/whatever. could this problem be because of some specific setup you did?
The problem is that it won't find a locale for the path guesser, but it will find a locale for the browser guesser, which is different than the cookie setting, thus triggering a change.
edit "fixed" the issues by giving cookie higher priority in the guesser list
The call to _wdt route triggers a new locale update. If for instance your url schema is /nl/news but your browser is set to 'en_US', the "normal" request will set the locale to 'nl', but the dev route (without locale) will set the locale back to 'en_US', which in case you use a cookie will trigger 2 changes: first the correct 'nl', then the incorrect 'en_US'
The text was updated successfully, but these errors were encountered: