Project

General

Profile

Actions

Bug #106152

open

Restoring records does not check for valid slugs

Added by Josef Glatz about 1 month ago. Updated about 1 month ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
DataHandler aka TCEmain
Target version:
Start date:
2025-02-11
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
datahandler, slug, integrity, recycler
Complexity:
Is Regression:
Sprint Focus:

Description

Problem/Description

TYPO3 does not check for any resulting inconsistencies of record slugs. The datahandler is is used to undo / restore records but is NOT using \TYPO3\CMS\Core\DataHandling\DataHandler::fixUniqueInSiteForSubpages method to verify and update restored slugs.

how to reproduce (simple example)

1. Create a pagetree

site/subpage/subpage

2. delete subpage in first level

site/subpage and childrens

3. create a new page with slug site/subpage

4. restore the previously deleted pages

with activated recursive restore checkbox

5. you have now to pages with the same slug site/subpage

ToDo(s)

  • Restored records (just pages or also any record with a defined slug field??) must have a consistent unique (site or whole TYPO3 instance wide) slug.
  • The backend user needs to be informed about the slug inconsistence and the changed records

Acceptance Criteria

A restored records must not have a conflicting slug in general

Actions #1

Updated by Josef Glatz about 1 month ago

  • Description updated (diff)
  • TYPO3 Version changed from 13 to 12
Actions #2

Updated by Josef Glatz about 1 month ago

  • Description updated (diff)
Actions #3

Updated by Josef Glatz about 1 month ago

  • Priority changed from Should have to Must have
Actions #4

Updated by Georg Ringer about 1 month ago

  • Category changed from Recycler to DataHandler aka TCEmain
  • Tags changed from datahandler, slug, integrity to datahandler, slug, integrity, recycler
Actions

Also available in: Atom PDF