Task #89301

Streamline automatic slug & redirects handling

Added by Oliver Hader almost 2 years ago. Updated 8 months ago.

Status:
Accepted
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Start date:
2019-09-29
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Issue #89115 introduce automatic slug handling as a new feature (which is great). However, there are a couple of things that need to be streamlined

  • probably refactor or even merge SlugService into according DataHandler hook
  • get rid of disableHook, enableHook calls (currently in SlugService) - but still avoid nested hook invocations (hook calling itself)
  • enhance test cases, consider using YAML scenario having more levels in the page tree
  • introduce sys_redirects loop detection, e.g. a -> b -> c -> a (in this case (temporary) redirects created in between could be reverted)
  • introduce UI component (settings currently only can be modified using config.yaml directly)

Related issues

Related to TYPO3 Core - Feature #89115: Auto-create Redirects on Slug ChangesClosedFrank Naegler2019-09-09

Actions
Related to TYPO3 Core - Task #89325: Prevent duplicate redirects in backend moduleNew2019-10-01

Actions
Related to TYPO3 Core - Bug #89326: Prevent duplicate redirects in auto redirectsAcceptedFrank Naegler2019-10-01

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

Actions
Related to TYPO3 Core - Bug #89328: Auto redirect does not respect language hostUnder ReviewFrank Naegler2019-10-01

Actions
Related to TYPO3 Core - Feature #93288: Merge redirect chainsNew2021-01-14

Actions
Related to TYPO3 Core - Task #93294: Improve automatic slug handlingNew2021-01-15

Actions
Related to TYPO3 Core - Bug #91936: Documentation missing to disable automatic creation of redirects on slug changeNeeds Feedback2020-08-05

Actions
Related to TYPO3 Core - Bug #91792: Automatically created redirects are not created using the DataHandlerNew2020-07-13

Actions
Related to TYPO3 Core - Feature #92004: Create redirect entry if updated slug is published to liveNew2020-08-14

Actions
Related to TYPO3 Core - Feature #93545: Inverse the behaviour of redirect creation after slug updateNew2021-02-18

Actions
Related to TYPO3 Core - Bug #91557: Auto slug update creates not working redirectAccepted2020-06-03

Actions
Related to TYPO3 Core - Bug #94003: Automatic update of subpages slugs not working for copy of subtreeNew2021-04-28

Actions
Related to TYPO3 Core - Bug #94004: Automatic update of subpages slugs ignores columnsOverridesNew2021-04-28

Actions
Related to TYPO3 Core - Bug #93370: Redirects: non-admin users can not revert redirects via popup (although BE notification claims otherwise)Accepted2021-01-26

Actions
#1

Updated by Oliver Hader almost 2 years ago

  • Category set to Link Handling, Site Handling & Routing
#2

Updated by Oliver Hader almost 2 years ago

  • Related to Feature #89115: Auto-create Redirects on Slug Changes added
#3

Updated by Oliver Hader almost 2 years ago

  • Description updated (diff)
#4

Updated by Oliver Hader almost 2 years ago

  • Description updated (diff)
#5

Updated by Guido Schmechel almost 2 years ago

  • Related to Task #89325: Prevent duplicate redirects in backend module added
#6

Updated by Guido Schmechel almost 2 years ago

  • Related to Bug #89326: Prevent duplicate redirects in auto redirects added
#7

Updated by Guido Schmechel almost 2 years ago

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

Updated by Guido Schmechel almost 2 years ago

  • Related to Bug #89328: Auto redirect does not respect language host added
#9

Updated by Sybille Peters 8 months ago

You mentioned:

introduce sys_redirects loop detection, e.g. a -> b -> c -> a (in this case (temporary) redirects created in between could be reverted)

There are redirect loops, but there are also redirect chains (without loops), e.g.

a -> b -> c

Would be good if these can be handled as well, see #93288

And there are duplicates, see #89325. #89326

I am not sure, if all this handling can or should be done on the fly. It would already help a lot if there were a command which would clean up all of these. (however the conflicts may be a bit difficult). I assume this should be much easier to implement.
There is already a redirect:cleanup command.

#10

Updated by Sybille Peters 8 months ago

#11

Updated by Torben Hansen 8 months ago

  • Related to Task #93294: Improve automatic slug handling added
#12

Updated by Daniel Goerz 6 months ago

  • Related to Bug #91936: Documentation missing to disable automatic creation of redirects on slug change added
#13

Updated by Daniel Goerz 6 months ago

  • Related to Bug #91792: Automatically created redirects are not created using the DataHandler added
#14

Updated by Daniel Goerz 6 months ago

  • Related to Feature #92004: Create redirect entry if updated slug is published to live added
#15

Updated by Daniel Goerz 6 months ago

  • Related to Feature #93545: Inverse the behaviour of redirect creation after slug update added
#16

Updated by Daniel Goerz 6 months ago

  • Related to Bug #91557: Auto slug update creates not working redirect added
#17

Updated by Sybille Peters 4 months ago

  • Related to Bug #94003: Automatic update of subpages slugs not working for copy of subtree added
#18

Updated by Sybille Peters 4 months ago

  • Related to Bug #94004: Automatic update of subpages slugs ignores columnsOverrides added
#19

Updated by Sybille Peters 4 months ago

  • Related to Bug #93370: Redirects: non-admin users can not revert redirects via popup (although BE notification claims otherwise) added

Also available in: Atom PDF