Project

General

Profile

Actions

Bug #86747

open

Using PersistedPatternMapper has some drawbacks

Added by Chris Müller about 6 years ago. Updated over 4 years ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
Site Handling, Site Sets & Routing
Target version:
-
Start date:
2018-10-26
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

I configured the route of an extension's single page in my config.yaml of the site management with the help of the PersistedPatternMapper:

routeEnhancers:
Person:
type: Extbase
limitToPages: [67]
extension: Person
plugin: Pi1
routes:
- { routePath: '/{name}', _controller: 'Person::show', _arguments: {'name': 'person'} }
aspects:
name:
type: PersistedPatternMapper
tableName: 'tx_person_domain_model_person'
routeFieldPattern: '^(?P<given_name>.+)-(?P<last_name>.+)$'
routeFieldResult: '{given_name}-{last_name}'

I am facing now two problems:

  • In the generated URL for the single page the result ({given_name}-{last_name}) is not in lower case like the other parts of the slug (the result is e.g. "John-Doe" instead of "john-doe").
  • When using umlauts the slug is e.g. "Mäx-Müstermänn" instead of "maex-muestermaenn".

Hint: In the given example the < and > chars are converted from Redmine to &lt; and &gt;.


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Bug #86797: No field value tranformation/URL sanitation when using extbase extension custom field as a route path segmentNew2018-10-30

Actions
Actions

Also available in: Atom PDF