#90531Requirements are not considered when an aspect is present
Description
Follow up of: #86895
Now that requirements are not considered when an aspect is present a whole of our sites did break.
We have a customly programmed aspect (used in the ExtbasePluginEnhancer) which considered slashes and resolved the URL by itself (by exploding the slashes and finding the correct uid of the dataset). To make this work I did set the requirements to .* (because the default requirement [^/]++ forbids slashes). We did this to have arbitrarily deep category trees which are represented in the url.
This change totally breaks this, because I can not set the requirements anymore (exception about [^/]++ because a slash is present). What is the solution for me here?
How do I resolve custom URLs containign slashes? I do not find any documentation or tutorials for this as well.
Reviews 2
Related issues 6
- Bug #86895routeEnhancer not working correct for paginate widget
- Bug #87333Slug fieldSeparator default value collides with symfony strict requirements
- Bug #88291Exception thrown if slash in route field of PersistedPatternMapper aspect
- Bug #89263TCEMAIN.preview doesn't work for routed controller with empty arguments
- Bug #91246routeEnhancer defaults not applied in TYPO3 v9.5.16
- Bug #916339.5.19 breaks formerly working routeEnhancer