I’m not sure if we did something wrong in recent upgrade to 2.3.3, any input on solving the mystery is welcome.
After our standard upgrade from 2.3.2 to 2.3.3 some of our users complained that they cannot interact with the pages, buttons or menus did not do any action. For many other users things were working fine. After some debugging we found that for problematic users browser fails to load
en_US-react.js files, but in successful cases the files that were loaded successfully were named
en_GB-react.js. Turns out that users that have
en_US in their language settings all have problems now. As a workaround I updated database for those unlucky users and replaced en_US with en_GB. I tried to understand how
en_US.js is served, but apparently it is something dynamically generated, I’m not sure I can follow how that request is handled.
Did anything related to localization changed in 2.3.3? (And I hope US was not banned from Indico entirely?)