Project

General

Profile

Actions

Bug #87667

open

Replacements not applied for existing slug

Added by Mathias Brodala about 5 years ago. Updated about 2 years ago.

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

0%

Estimated time:
TYPO3 Version:
12
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 2 (0 open2 closed)

Related to TYPO3 Core - Bug #86740: Using slash in slug in extension record throws exception in frontendClosed2018-10-25

Actions
Related to TYPO3 Core - Bug #88291: Exception thrown if slash in route field of PersistedPatternMapper aspectClosed2019-05-07

Actions
Actions #1

Updated by Mathias Brodala about 5 years ago

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

Updated by Mathias Brodala about 5 years ago

  • Assignee deleted (Mathias Brodala)
Actions #3

Updated by Benni Mack almost 5 years 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

Actions #4

Updated by Benni Mack almost 5 years ago

  • Target version changed from next-patchlevel to Candidate for patchlevel
Actions #5

Updated by Daniel Reichel almost 5 years ago

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

Updated by Susanne Moog almost 4 years 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?

Actions #7

Updated by Benni Mack over 3 years ago

Ping, can you please be more specific to the questions we asked? Otherwise I'll close this issue.

Actions #8

Updated by Christian Kuhn about 2 years ago

  • Status changed from Needs Feedback to Closed

hey. i hope it's ok to go ahead and close here for now.

Actions #9

Updated by Mathias Brodala about 2 years ago

  • 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.

Actions

Also available in: Atom PDF