In a page with Content translation enabled, the 'URL path' and 'Path prefix' don't work properly.

  • The name in 'URL path settings' only gets used sometimes instead of the node number. This happens both for the default, and for the translated language.
  • The same applies to the 'Path prefix' (admin/settings/language/edit/es). It gets used only sometimes. The path prefix for the default language (admin/settings/language/edit/en) never gets used here, and for one page, it even uses the prefix "es" for the default English language instead of "en".

My settings:

  • 'Locale' and 'Content translation' modules activated.
  • Added the language Spanish (admin/settings/language/add).
  • 'Multilingual support: Enabled, with translation' (admin/content/node-type/page).

Comments

gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented
Status: Active » Postponed (maintainer needs more info)

What's needed information here is your language negotiation settings. Please tell us about that.

jjalocha’s picture

jjalocha commented

Thank you, Gábor, for your reply.
I just changed from 'Path prefix only' to 'Path prefix with language fallback', and the prefix for the default language started working immediately. I am using a default English page, with Spanish translation.

The other Issue I experienced was that sometimes the English pages were displayed with the 'es' prefix. This happened many times, but I never understood exactly how this was triggered. I think it happened somehow after opening the 'edit page' tab, but not saving any changes, and visiting the home page, which is a "fixed" page, called 'home'.

This last bug doesn't occur since I installed 'internationalization' from the i18n module.

ogi’s picture

ogi commented

subscribe

arhak’s picture

arhak commented

Which is the language of your browser?
I have notice that policies are giving some preferences to browser language.
BTW, when you navigate to your fixed homepage, which language do you expect the links would be?
The links can't be in both language neither guess what do you want.
I think the problem is just right there. After going to your homepage the policy for selecting a language is mis-prioritized, I mean, it's not inferring the language as expected.
I was playing around with the third option ("Path prefix with language fallback") and it states the following priorities:
- URL prefix
- User's language
- Browser's language
Which doesn't makes any sense since the user will always have a language, so the browser's language goes actually first (indeed)
About the second option ("Path prefix") it didn't worked as I expected so I took the third.
PS: Be careful when you think an English page is showing up under "es" prefix, I think it's probably a Spanish page partially translated, so there are many stuff in English.

dpearcefl’s picture

dpearcefl commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Closing this issue because of a lack of activity.