#88715Wrong routes for default url slugs on translated base path pages
Description
We have configured a multi lanugage setup with the following structure (see site configuration image attachment):
- de: http://dev.example.com/de/
- en: http://dev.example.com/
- es: http://dev.example.com/es/
- fr: http://dev.example.com/fr/
So the default language in the backend of TYPO3 is german, but the URL for german contains “de”. This is exactly what we want and it works as expected, but a strange side effect is also present afterwards, because something like this is working, too:
- de: http://dev.example.com/de/kontakt (fine)
- en: http://dev.example.com/contact (fine)
- en: http://dev.example.com/kontakt (bad)
As you can see routes to the default pages will be created for translated pages too if they don’t contain a language parameter like “en”. So if someone visit http://dev.example.com/kontakt he will get the same content as http://dev.example.com/contact. So canoncial link is set to the right URL and SEO will not be affected, but this pages or routes should not be generated instead.
Reviews 5
- 11.5 79705[BUGFIX] Resolve page with trailing slash requested without one
- 12.4 79679[BUGFIX] Resolve page with trailing slash requested without one
- main 79249[BUGFIX] Resolve page with trailing slash requested without one
- 11.5 76494[BUGFIX] Prevent resolving translated page with default slug
- main 75101[BUGFIX] Prevent resolving translated page with default slug
Related issues 3
- Bug #96010Translated pages can be loaded with slug of default language
- Bug #99554After I've installed patch lvl 11.5.18, mount points with non translated slugs stoped working and shows 404 in the FE.
- Bug #100990Pages with trailing slash in slug are not resolved if requested uri does not contain a trailing slash