Bug #87667
open
Replacements not applied for existing slug
Added by Mathias Brodala almost 6 years ago.
Updated over 2 years ago.
Category:
Site Handling, Site Sets & Routing
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 to Bug #86740: Using slash in slug in extension record throws exception in frontend added
- Assignee deleted (
Mathias Brodala)
- 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
- Target version changed from next-patchlevel to Candidate for patchlevel
- Related to Bug #88291: Exception thrown if slash in route field of PersistedPatternMapper aspect added
Is this issue about a one time update of existing slugs with new replacements (so basically re-generation of them all) or something more?
Ping, can you please be more specific to the questions we asked? Otherwise I'll close this issue.
- Status changed from Needs Feedback to Closed
hey. i hope it's ok to go ahead and close here for now.
- Status changed from Closed to New
- Priority changed from Must have to Should have
- TYPO3 Version changed from 9 to 12
Christian Kuhn wrote in #note-8:
hey. i hope it's ok to go ahead and close here for now.
Actually no, I completely missed notifications for this one.
As long as the replacements are only applied in SlugHelper::generate() (thus only for records without slug) instead of SlugHelper::sanitize() (thus for any record), this issue still prevails.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by