Skip to content

fix: remove non-existent 'settings' i18n namespace (splash screen 404)#1581

Closed
andersondario-er wants to merge 1 commit into
release-2.139.1from
ERCS-7240
Closed

fix: remove non-existent 'settings' i18n namespace (splash screen 404)#1581
andersondario-er wants to merge 1 commit into
release-2.139.1from
ERCS-7240

Conversation

@andersondario-er
Copy link
Copy Markdown
Contributor

Summary

Removes 'settings' from the preloadNamespaces list in src/i18n.js. The file public/locales/en-US/settings.json (and all other locales) has never existed in the repo, and no component uses this namespace. The app was broken by the i18next v25→v26 upgrade (Apr 27, 2026): v26 treats a 404 on a preloaded namespace as a fatal init failure, blocking the app at the splash screen.

Changes

  • Remove 'settings' from preloadNamespaces in src/i18n.js — the file never existed, the namespace is unused

Technical Details

  • Symptom: 404 /locales/en-US/settings.json?v=1.39 → app never loads past splash screen
  • Root cause: 'settings' was added to preloadNamespaces in Feb 2024 without a corresponding settings.json file; i18next v25 silently skipped 404s, v26 does not
  • Affected: any tenant running release-2.139.1 (e.g. birdlifezimbabwe.pamdas.org)
  • No translation content is lost — zero components reference this namespace

Files Changed

  • src/i18n.js — remove 'settings' from preload namespace list

Fixes ERCS-7240

The 'settings' namespace has been listed in preloadNamespaces since at
least Feb 2024 but the corresponding settings.json file was never
created in public/locales/. No component uses this namespace either.

In i18next v25 this was silently ignored. After the v25→v26 upgrade
(Apr 27, 2026) a missing preloaded namespace blocks i18n initialisation,
preventing the app from loading past the splash screen.
@andersondario-er andersondario-er deleted the ERCS-7240 branch May 28, 2026 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant