#88291Exception thrown if slash in route field of PersistedPatternMapper aspect
Description
In my site configuration I have configured a aspect of type PersistedPatternMapper for the detail view of a record of my custom extension.
If the configured route field contains a slash, a error occurs in the frontend.
exception.jpg
You can reproduce the bug using the news extension. I know, the news extension has a slug field but my custom extension which you dont’t have has not.
This is the site configuration:
routeEnhancers:
NewsPlugin:
type: Extbase
extension: News
plugin: Pi1
routes:
- { routePath: '/news/{news}', _controller: 'News::detail', _arguments: {'news': 'news_title'} }
defaultController: 'News::detail'
aspects:
news:
type: PersistedPatternMapper
tableName: 'tx_news_domain_model_news'
routeFieldPattern: '^(?P<title>.+)-(?P<uid>\d+)$'
routeFieldResult: '{title}-{uid}'Reviews 2
Related issues 7
- Bug #86596Slash in Page Title still in URL
- Bug #87333Slug fieldSeparator default value collides with symfony strict requirements
- Bug #87656Slugs error if title has "/" in extbase extension
- Bug #87667Replacements not applied for existing slug
- Bug #89263TCEMAIN.preview doesn't work for routed controller with empty arguments
- Bug #90531Requirements are not considered when an aspect is present
- Feature #90814Allow slash in routeFieldResult and routeFieldPattern to allow optional paths