- 🇫🇷France anrikun
Don't you think it should be considered as a bug?
Why should translation language be the same as interface language when there are two separate langcodes in the URL?
I'm building a site using entity translation, and in the process of translating nodes, I find that it is annoying to the user for the language to switch when adding a translation. It's probably not the case for all sites, i.e. I can think of sites where it would be useful for the interface language to switch when adding a translation, but for my case, the opposite would work best.
So, in node/ID/translate the add/edit buttons for the translation get the URL language prefix, if URL detection is on. Deactivating URL detection does remove the prefixes, but is there a way to avoid the prefix without deactivating URL detection? That is, is there a way to translate the entity while keep the default language for the interface?
Active
Base system
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Don't you think it should be considered as a bug?
Why should translation language be the same as interface language when there are two separate langcodes in the URL?