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
After alot of trials, i have done the obvious and translated the whole block for different languages with each property condition as follows: ->propertyCondition('langcode', 'en...
How to get the current page language?
Thanks so much! It's working now: I was able to transfer the docroot files to the containing directory without the need for a second database or any manual configuration export/import/sync...
Backup & Migrate Config: There was a problem creating field...database table with the name already exists.
Ah, I see. Sorry, I hadn't clicked the link and assumed it was the instructions for upgrading from Drupal 7. If you are simply copying a site from one location on a server to another, the...
Backup & Migrate Config: There was a problem creating field...database table with the name already exists.