Bug #87667

Replacements not applied for existing slug

Added by Mathias Brodala over 1 year ago. Updated 2 months ago.

Status:
Needs Feedback
Priority:
Must have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Start date:
2019-02-06
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Since #86740 one can define replacments for slug fields, e.g. to get rid of slashes.

However, these are not applied for existing or predefined slugs, e.g. when creating pages through the DataHandler.

All replacements must be applied upon sanitation, no matter the source of the slug.


Related issues

Related to TYPO3 Core - Bug #86740: Using slash in slug in extension record throws exception in frontend Closed 2018-10-25
Related to TYPO3 Core - Bug #88291: Exception thrown if slash in route field of PersistedPatternMapper aspect Closed 2019-05-07

History

#1 Updated by Mathias Brodala over 1 year ago

  • Related to Bug #86740: Using slash in slug in extension record throws exception in frontend added

#2 Updated by Mathias Brodala over 1 year ago

  • Assignee deleted (Mathias Brodala)

#3 Updated by Benni Mack about 1 year ago

  • Status changed from New to Needs Feedback

Hi Mathias,

but if you want to get rid of "slashes" in an existing slug, then it would

generate on first time "/my/own/product/" and then on sanitization "/my-own-product/" - right?

Do you have a clever idea on how to solve this?

All the best,
Benni

#4 Updated by Benni Mack about 1 year ago

  • Target version changed from next-patchlevel to Candidate for patchlevel

#5 Updated by Daniel Reichel about 1 year ago

  • Related to Bug #88291: Exception thrown if slash in route field of PersistedPatternMapper aspect added

#6 Updated by Susanne Moog 2 months ago

Is this issue about a one time update of existing slugs with new replacements (so basically re-generation of them all) or something more?

Also available in: Atom PDF