Description of the need
Currently the 404 and 403 page setting isn't translatable, so all languages on a multilingual site get the same path. Even it that page is a translated node.
Proposed solution
We could either add per-language settings if the language module is installed, or we could follow the node translation if the page is a node and translations exist.
Alternatives that have been considered
- A layout (single path) that uses the translated node as "existing content"
- Contrib module
Both don't seem ideal, as the former requires some knowledge of the layout system, the latter requires people to know about the module.
Is there a Drupal or Backdrop contributed module that accomplishes this?
i18n does that for D7 (with bad UX), but that feature requires the (unported / unportable) Variables module for i18n_variables.
Additional information
This popped up in the i18n (contrib) issue queue.
See this comment for the steps to do it with a layout. We can't assume, a Backdrop newbie is able to do this.
Recent comments
There is a Drupal 7 contrib module that "lets the administrator see all administration pages in her preferred language" and which could be ported to Backdrop: https://www.drupal.org/project/...
Allow admin to select admin language seperate from front end language (multilingual)
@stpaultim – You're right: my approach affects also the main menu. I guess, because menus are also considered as user interface (not as content). @findlabnet – If I didn't miss anything,...
Allow admin to select admin language seperate from front end language (multilingual)
Go to the account edit of the desired user. On the horizontal tab below "Region and Language," select "English" or another language. WFM.
Allow admin to select admin language seperate from front end language (multilingual)