While testing
✨
Path alias filter by system path
Needs work
I've noticed if you create an URL alias on /admin/config/search/path/add for an already existing node on a site that has installed only a single language and you install the language module afterwards adding a second language you will end up with with None entries in the language column on /admin/config/search/path for those nodes.
Node:
/node/add/article and add title cat add /animal in the url alias section in the advanced column and save/node/add/article and add title apple and /fruit in the url alias section in the advanced column and saveLanguage and the Content Translation module/admin/config/regional/language /admin/config/search/path=> The entries in the language column show English
URL alias
/node/add/article and add title cat and save. Is node 1/node/add/article and add title apple and save. Is node 2/admin/config/search/path/add, use /node/1 for the system path and animal for the URL alias/admin/config/search/path/add, use /node/2 for the system path and fruit for the URL aliasLanguage and the Content Translation module/admin/config/regional/language /admin/config/search/path=> The entries in the language column show None
The case outlined for URL alias in the steps to reproduce section should behave like the Node case and also end up showing the language the node was created in instead of showing None
Active
11.0 🔥
This is due to the standalone admin form for aliases always creating aliases as language-neutral whilst the site is monolingual. See #2484411: Manual path aliases are not the same as aliases on the node form on single-language sites → .