No « save as English » button in a Multi-lingual site.

[PierDuSud]

Hello All,
I seek help with the configuration of multi-lingual management in the admin backend.

Setup, Problem and Behaviour

• Two multilanguage pages are in the directory 01.home: default.en.md and default.fr.md.
• The configuration of system.yaml is pasted below.
• The site shows both pages with the [base_url]/en and [base_url]/fr.
• The admin page loads the french page, but shows 0 translations for the page.
• In the admin page, when clicking on the language switcher button (e.g. EN button), I get the warning « No English translation exists. Viewing Français fallback. Use "Save as English" to create a translation you can edit. »
• There is no « Save as English » button.

Any ideas on how to solve this?

Config

custom_base_url: '[redacted]'
languages:
supported:
- en
- fr
default_lang: fr
content_fallback:
en:
- en
- fr
fr:
- fr
pages:
theme: learn2
append_url_extension: null
redirect_default_code: '302'
cache:
redis:
socket: null
errors:
display: 1
debugger:
token: null
images:
cls:
retina_scale: '1'
gpm:
verify_peer: true
updates:
safe_upgrade: true
safe_upgrade_snapshot_limit: 5

[rhukster]

Thanks for the detailed write-up @PierDuSud. I set up a site with your exact language settings and a page with default.en.md and default.fr.md, and the admin showed both translations with the normal Save button, so something specific to your install is different. Could you share:

1. Your Grav, Admin2 and API plugin versions
2. The exact file names in that page's folder (including any default.md)
3. In your browser's developer tools Network tab, the response to the /pages/home?lang=en&translations=true request (the language, translated_languages and untranslated_languages fields are the ones that matter)

That will tell us whether the admin or the server is getting it wrong. It's also worth running bin/grav clear and reloading the admin once first.

[PierDuSud]

Hi @rhukster , thanks for the follow-up. As requested:

1. As per the admin info: Grav: 2.2.3; Admin2: 2.2.26; API: 1.0.43.
2. The pages in 01.homeare default.en.mdand default.fr.md. (Both owned by www-data). There is nothing else in the directory (no default.mdfile).
3. For https://[base_url]/admin/pages/home?lang=en&translations=true, I get 404 not found. Maybe you mean https://[base_url]/admin/pages?lang=en&translations=true. In which case, I get lang: en and translations: true, but no translated_languages and untranslated_languages attributes. See the image below.

I ran bin/grav clear from the root directory and reloaded the admin pages. Same behaviour. I should add that the admin backend loads default.fr.md in both languages, regardless of the default.en.md in the directory.

Thanks for your help.

[rhukster]

Thanks @PierDuSud, that helps a lot. The address I pointed you at wasn't clear, sorry about that. Here is a simpler check that needs no developer tools and no login.

Open this in your browser, replacing the first part with your site address (the same one you use for /en and /fr):

https://YOUR-SITE/api/v1/translations/en?prefix=ZZZ

If you see one short line ending in "count":0, ... "strings":[], that part is fine. If you see a very long page of text with a count in the thousands, your web server is not passing the query string (the part after the ?) through to Grav. I can reproduce exactly what you describe that way: the admin asks for the English version, Grav never sees the request for English, and it returns the default French page with no translation list.

Could you tell me which of the two you get, which web server you use (nginx, Apache, Caddy), and whether there is a proxy in front of it? If it's nginx, please paste the location / block of the site config. The line should read:

try_files $uri $uri/ /index.php?$query_string;

A line that ends in /index.php; without the ?$query_string part causes this.

One caution until this is sorted: avoid saving the home page while the admin is switched to EN, because the save would go into the French file.

[PierDuSud]

Hi @rhukster , thanks for the follow-up.

• I did do the API request and I get a count of 2899, so I guess you have pinpointed the issue.
• I am using nginx. There is no proxy server in front of it and PHP files are rendered through php8.5-fpm.sock.
• The location block is pasted below, and indeed has a missing $.

location / { try_files $uri $uri/ /index.php?query_string; }

I have corrected the missing $ sign and reloaded nginx. Now:

• The API returns a 0 count call.
• The « save as [language] » button now shows up.
• All seems normal.

A silly typo. Thanks for helping me finding it out. :)

Pier

[rhukster]

Glad that sorted it @PierDuSud, and thanks for checking so carefully. That one-character typo is easy to miss, so the next Grav release (2.2.5) reads the query string from the request address when the web server doesn't pass it on, and the admin editor will say clearly when it couldn't load the language you picked instead of pointing at a button that isn't there.