Project

General

Profile

Actions

Bug #102137

open

Problems due to automatic redirects

Added by Björn Jacob 8 months ago. Updated 8 months ago.

Status:
Needs Feedback
Priority:
Should have
Assignee:
-
Category:
Redirect Handling
Target version:
-
Start date:
2023-10-10
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
12
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When you regenerate the URL segment for a page, a redirect is automatically created. This can cause redirects / a redirect loop. The editor will not notice because no warning is displayed.

  1. Scenario

A possible scenario (which happens in real life and can be reproduced easily):

  • editor copies page "X" -> new name "X1"
  • generated slug: "/x-1"
  • editor renames page "X1" to "Y"
  • generated slug: "/y"
  • auto-generated redirect: "/x-1" auf "/y"
  • editor renames page "Y" to "Z"
  • generated slug: "/z"
  • auto-generated redirect: "/y" auf "/z"
  • editor creates a new page "Y"
  • generated slug: "/y"
  1. Result

Page "Y" is not accessible because the redirect from "/y" to "/z", which was automatically generated earlier, is still active.

  1. Current solution

Editor has to open the list of redirects and look for the corresponding entry. After that, the editor has to delete the redirect and everything works as expected.

It would be great if there could be checks installed which will warn the editor about this scenario and behaviour.


Related issues 2 (1 open1 closed)

Related to TYPO3 Core - Feature #99485: Show the redirect integrity statusClosedGuido Schmechel2023-01-07

Actions
Related to TYPO3 Core - Task #89301: Streamline automatic slug & redirects handlingAccepted2019-09-29

Actions
Actions #1

Updated by Björn Jacob 8 months ago

Actions #2

Updated by Stefan Bürk 8 months ago

The middleware should detect that loop, fullfilled by pure
`ext:redirects` records and dropping the redirect(not doing)
it - along with logging it to the log.

Additionally, the integrity check should detect that. There
is a pending patch #99485 to make that integrity status visible
and searchable/fiterable in the admin/backend module (later on).

However, if a editor changes a page slug a normal notification
should appear if auto-redirect creation is enabled, at least
the core version. That misses a redirect loop detection at that
specific point.

Due to talks with quite some people, it's clear that that notification
is already not really understood by editory and adding that sentence
would not really help here.

Beside some contributor efforts now, I have some features in mind for
v13 to enhance the visibility of these redirects on pages - will see
how it pays out. Beauce of planing and timing thats scheduled for a
later point in the v13 development cycle (after 13.0 / 13.1).

I had quite some issue to understand this issue first, if this is now
what really:

  • bug-report: what's not working excalty ? Redirects not created,
    Endless Loop Detection and Preventing in the Middleware broken ?
  • feature-request: Enhance visibility, notifcation etc
Actions #3

Updated by Stefan Bürk 8 months ago

  • Status changed from New to Needs Feedback
Actions #4

Updated by Markus Klein 7 months ago

  • Related to Task #89301: Streamline automatic slug & redirects handling added
Actions

Also available in: Atom PDF