Bug #97468
open
RouteEnhancer ignores db tables when slug option "unique" is used
0%
Description
Hey,
it seems that there is a problem with the "unique" slug option and RouteEnhancers when different db tables use the same string in the slugs.
I used the "unique" option for slug fields for a webpage with multiple site configurations to be able to display projects and news on both sites.
In my case there is a project and a news with the same name, e.g. slug => "test".
If several projects have "test" then a "-1" is added, so no problem at this point.
However, when a news and a reference have the same name, the RouteEnhancer seems to ignore in which table the slug is unique.
In the view of the listAction I display all news.
But when I click the showAction link, the action parameter for the domain model is always "null".
But only as long as the RouteEnhancer is not commented out in the yaml file.
This problem only occurred when I used "unique".
I had no errors with "uniqueInSite" or "uniqueInPid".
If I remove the RouteEnhancer again, it works again.
Updated by Bastian Bringenberg over 2 years ago
- Project changed from 9 to TYPO3 Core
- Category deleted (
Development) - TYPO3 Version set to 11
Moved Project.
Guessed TYPO3 Version.
Updated by Christian Dorka over 2 years ago
Bastian Bringenberg wrote in #note-1:
Moved Project.
Guessed TYPO3 Version.
Yes the TYPO3 version in use is 11.5.9