Feature #93288

Merge redirect chains

Added by Sybille Peters 9 months ago. Updated about 18 hours ago.

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

0%

Estimated time:
PHP Version:
Tags:
redirects,redirect chains,cleanup redirects
Complexity:
Sprint Focus:

Description

Update

Oct 16, 2021

Since behaviour has now been changed to use a page link as target (e.g. t3://page?uid=123) and not a path, redirect chains should no longer be created by automatic redirect creation. They might however still be created manually and there is the question of the older redirects already existing.

Clarification of terms

I am talking about redirect chains here, not redirect loops.

chain : example:

  • /a => /b, /b => /c
  • /a => /b, /b => /c, /c => /d

2 (or more) redirects have to be followed now for redirecting to the final page. If one of the redirects is removed, the chain breaks

loop : example

  • /a => /a
  • /a => /b, /b => /a

Description

If slugs are changed several times, redirect chains are used to be created by automatic redirect creation, e.g. /a -> /b -> /c.

If these are merged, it reduces the number of requests necessary to load a page.

Could be done on-the-fly or as a command.

Before :

/a -> /b
/b -> /c

After

/a -> /c
/b -> /c

NEW: The behaviour has now been changed to use page links as targets, so the result would now be:

/a -> t3://page?uid=111
/b -> t3://page?uid=111

Related issues

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

Actions
Related to TYPO3 Core - Bug #93287: Avoid creation of unnecessary redirects on Slug changesNew2021-01-14

Actions
Related to TYPO3 Core - Bug #92748: Infinite redirects (redirect loop) when updating slugsNew2020-11-02

Actions
Related to TYPO3 Core - Bug #89327: Auto redirect: Could not resolve target pageClosedFrank Naegler2019-10-01

Actions
#1

Updated by Sybille Peters 9 months ago

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

Updated by Sybille Peters 9 months ago

  • Related to Bug #93287: Avoid creation of unnecessary redirects on Slug changes added
#3

Updated by David Bruchmann 9 months ago

  • Related to Bug #92748: Infinite redirects (redirect loop) when updating slugs added
#4

Updated by Sybille Peters 8 months ago

  • Description updated (diff)
#5

Updated by Sybille Peters 6 months ago

  • Related to Bug #89327: Auto redirect: Could not resolve target page added
#6

Updated by Sybille Peters 6 months ago

If not the path, but the page id (or t3://page?id=ID) is used as target, this would no longer be a problem. See #89327

#7

Updated by Sybille Peters about 18 hours ago

  • Description updated (diff)
#8

Updated by Sybille Peters about 18 hours ago

  • Description updated (diff)

Also available in: Atom PDF