Broken localisation after syncing data on startup

[Basti-Fantasti]

Hi all,

I have set up the wger server using the provided docker compose file for the 'prod' environment
After enabling these two parameters in the prod.env:

SYNC_EXERCISES_ON_STARTUP=True
DOWNLOAD_EXERCISE_IMAGES_ON_STARTUP=True

and restarting the containers, all German translations are gone.
I call the '/de' route, but the UI shows in the main content of the site (Top Menu is translated fine) only the string variable names like:

• routines.routines
• nothingHereYetAction
• nutrition.plans

etc

How can I get the proper German translation back?

Thanks in advance

UPDATE 1: The same issue is on all translations.
I've opened the /en route and I also get only the variables like shown above

[rolandgeider]

hi! that sounds like a problem with the react files. Can you open the browser's developer console and see if there's a bunch of 404s trying to get "translation.json"?

[Basti-Fantasti]

you've nailed it 👍

Do I have to rebuild something or set a specific parameter for the updates to be done?

[Basti-Fantasti]

I've set the domains for STATIC_URL and MEDIA_URL as suggested to the absolute paths on my public domain.

The same error comes up when calling the site using http and the local ip.

[Basti-Fantasti]

I've now reverted some config changes in my prod.env and made it work locally.
Now I need to check my Nginx Proxy Manager settings.
Maybe some issues with the static folder...
But the 404 are gone

[Basti-Fantasti]

Looking good now.
I had to add two custom locations on my NPM Proxy Host config

location: /static
Scheme: http
Forward Hostname: <mydockerhostip>/static
port: as exposed, default 80


location: /media
Scheme: http
Forward Hostname: <mydockerhostip>/media
port: as exposed, default 80

[rolandgeider]

glad you got it working! While the handling of the static files is not rocket science (collect them and let the server actually serve them), there's so much that can go wrong and break things in subtle ways