Can't translate content anymore

Thank you, @interactivex, for reporting this issue.

I have investigated the problem, and it seems that you have enabled the fallback mechanism under Configuration > Region and Language > Languages > Language-Country Fallbacks. This setting allows pages to be displayed with a fallback translation.

For example:

• Suppose Canada is set up with English and French as available languages.
• Node A has only an English translation.
• Accessing /en-ca/node-a will display the English translation with an English interface.
• Accessing /fr-ca/node-a will display the fallback English translation with a French interface.

On the /fr-ca/node-a we will see the edit link (/fr/node/x/edit). Edit page displays the source translation with a French interface instead of allowing the creation of a new French translation. However, this is a Drupal behavior and not a bug in the module.

We can disable the module and check that:

/fr/node/x/edit displaying the French translation if it exists.
/fr/node/x/edit displaying the source translation if the French translation does not exist.

Please let me know if you need further clarification.

Hi Anna D,

I tried your solution above to disable the fallback language, but unfortunately, it didn’t work. I’ve added a screen recording so you can see the issue. The problem is that when I enter the backend to edit a translation, the system doesn’t recognize the language. For example, in the admin environment, the /en-nl or /nl-nl prefix is missing from the URL.

I think it has to do with the option "Exclude admin pages" is enabled and I can't disable it (see screenshot). Although there is a remark below that says "Not used, yet."

Hello Jessica Denkelaar,

Thank you for providing the screen recording.

Language-Country negotiation does not work on admin pages. I suggest enabling and configuring "URL (Path prefix)" and placing it after Language-Country negotiation so that LCN has higher priority. If the problem persists, try disabling "Account Administration Language" to see if the issue still occurs.

Please keep us posted.

@interactivex, we added a new release to resolve ✨ Allow configuration option to include admin pages in negotiation Active . Please update the module and check whether this helps.

As Anna mentioned, your language negotiation configuration is rather unusual. Please note that the order of the negotiation plugins is essential. So judging by the screen recording, the "Selected language" negotiation plugin will always fire before the "Language-country URL" plugin. Note that the "Selected language" plugin is usually used as a fallback and placed at the end of the negotiation chain.

Further, when the "Exclude admin pages" configuration option is enabled in the language-country negotiation configuration, one needs a subsequent negotiation plugin to perform proper path processing.

Do not hesitate to follow up on this issue.