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
Thanks for the response, Herb! Since I posted that I did some more testing and have posted this issue https://github.com/backdrop-contrib/tfa_basic/issues/33 In fact, if both email...
TFA - how to setup fallback options 'per user'
I'll test this tomorrow to see if I can replicate the problem and report back. It's not "per user" so it should be working.
TFA - how to setup fallback options 'per user'
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list