Actions
Bug #104518
openPage resolution for additional language might fail for certain slugs
Status:
New
Priority:
Should have
Assignee:
-
Category:
Site Handling, Site Sets & Routing
Target version:
-
Start date:
2024-08-01
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
11
PHP Version:
7.4
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
If the entrypoint of the site configuration contains the name of a page slug in a language path, the page might not be found.
Steps to reproduce the bug:- create a site configuration with the entry point https://example.com/xyz
- entrypoint for the default language should be / (I have not tested it with other paths)
- entrypoint for the additional language should be /en/ (any other should work to, but this I tested)
- create the page "xyz" in the root page for the site configuration, the page should be available at https://example.com/xyz/xyz
- add a language variant for the page, which should be available at https://example.com/xyz/en/xyz
- if you try to access https://example.com/xyz/en/xyz you should get a 404 error
I am pretty sure the error is int the sorting in `TYPO3\CMS\Core\Routing\BestUrlMatcher::matchCollection`, as the relative slug `/xyz` is matched against the full path of the url
I tested this for version 11.5.38 but is probably in version 12 and 13, too, as the code seems the same
No data to display
Actions