FAQ
Every page is read-only and writes fail
The module starts with editable: false. Set editable: true in its antelope.config.ts entry and restart the backend. See Configuration.
The Project files workspace is empty or cannot be edited
Your frontend module is not flagged as the application layer. Add options: { dmsI18nAppLayer: true } to its AddFrontendModule call, and check that its locale files are named <name>-<xx-XX>.json (such as app-en-GB.json) under i18n/locales.
A key shows "From a module" in the project files
An installed module already translates that key. The text counts as translated. Write a value in the project files to override it; drop the override to return to the module's text.
The public URL answers 404
Only the workspaces you create are public. The project files and the installed modules are not served at /i18n/.... Check the workspace id (ids are case-insensitive) and the language code.
The public URL points to the wrong host
The URL is built on the DMS apiBaseUrl. Set it to the public origin of your backend.
Where are the workspaces I created stored?
In the i18n-workspaces/<workspace>/ folder of the installed module, one <locale>.json per language, unless you set workspacesDir. A reinstall of the module wipes that default folder: set workspacesDir to a folder of your project, and back it up (or use Download backup in the danger zone) before moving servers.
A new module's translations do not appear
The module reads the list of frontend modules again every couple of seconds, so a module registered after Lang started appears without a restart. Check that its files are named <name>-<xx-XX>.json under i18n/locales. Changes to files of a known module appear on the next read.
An edit landed in the wrong project file
With several project files per language, an existing key is written back to the file that defines it, and a new key to the file holding the longest part of its namespace, else to app-<xx-XX>.json. Put at least one key of a namespace in the file it belongs to, and new keys of that namespace follow it. See Project files.
I upgraded from a Nuxt-based setup: where did the locale path list go?
It is gone. The module now discovers locale files through the registered frontend modules; no locale path list or generated registry file is needed. Move the dmsI18nAppLayer flag from your old Nuxt configuration to the options of your AddFrontendModule call.
The module fails to load after an upgrade
Lang 0.2 requires @antelopejs/dms 0.9, @antelopejs/interface-dms 0.7 and the renderer @antelopejs/dms-frontend 0.6. Upgrade those dependencies together, or keep Lang ^0.1.0 on DMS 0.8. Troubleshooting covers dependency resolution and frontend integration errors.
The public files answer on the backend but not on the dashboard's origin
The frontend server (renderer 0.6) forwards only the backend prefixes declared to it. Lang declares /i18n/** itself; if the files still answer with a page, check that the dashboard runs Lang 0.2 or later and restart the frontend server so it reads the module's declaration again.