Bug #93328

redirect for empty slug

Added by David Bruchmann 9 months ago. Updated 2 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2021-01-20
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
7.3
Tags:
redirect, gui, interface, root-page
Complexity:
Is Regression:
Sprint Focus:

Description

Adding a slug to a page with before empty slug creates a redirect for the root-page and breaks so the whole site.
Considering #93327 I would at least get a warning about it but adding a redirect for the root-page without further automatic checks is devastating.
I propose a check for pages without slug and also if the current page had a slug before as requirement to create a redirect for those pages - including reasonable decisions based on the findings. Nevertheless, the final decision has to be shown for confirmation like described in #93327 as the proposed tests would be quite limited without further context.

#1

Updated by Andreas Kiessling 2 months ago

We just had this error on a site due to a misconfiguration of the editor role. They did not have the slug field after a core update, thus newly created pages had no slug. Later they were "fixed" and we ended up with automatically created root level redirects.
I tend to disable the automatic creation of redirects for all our setups, this is just too error prone and unintuitive.

Also available in: Atom PDF