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
Check out this post re: tempstore: https://forum.backdropcms.org/forum/tempstore-table
Which database tables can I saftely empty before DB backup
Hi. I use the "[node:title] | [site:name]" tokens for the main image of news articles, blog posts, and similar publications. It's a quick and practical automatic ALT.
How to Improve SEO Performance in Backdrop CMS
I understand how tokens work, but not so much their practical use in image alt/text (maybe caption?) text. Could you give an example or two?
How to Improve SEO Performance in Backdrop CMS