Task #89301
open
Streamline automatic slug & redirects handling
Added by Oliver Hader about 5 years ago.
Updated about 1 year ago.
Category:
Link Handling & Redirect Handling
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)
- Category set to Site Handling, Site Sets & Routing
- Related to Feature #89115: Auto-create Redirects on Slug Changes added
- Description updated (diff)
- Description updated (diff)
- Related to Task #89325: Prevent duplicate redirects in backend module added
- Related to Bug #89326: Prevent duplicate redirects in auto redirects added
- Related to Bug #89327: Auto redirect: Could not resolve target page added
- Related to Bug #89328: Auto redirect does not respect language host added
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.
- Related to Task #93294: Improve automatic slug handling added
- Related to Bug #91936: Documentation missing to disable automatic creation of redirects on slug change added
- Related to Bug #91792: Automatically created redirects are not created using the DataHandler added
- Related to Feature #92004: Create redirect entry if updated slug is published to live added
- Related to Feature #93545: Inverse the behaviour of redirect creation after slug update added
- Related to Bug #91557: Auto slug update creates not working redirect added
- Related to Bug #94003: Automatic update of subpages slugs not working for copy of subtree added
- Related to Bug #94004: Automatic update of subpages slugs ignores columnsOverrides added
- Related to Bug #93370: Redirects: non-admin users can not revert redirects via popup (although BE notification claims otherwise) added
- Related to Bug #93230: TYPO3 memory issues when changing slugs added
- Sprint Focus set to On Location Sprint
- Related to Bug #93287: Avoid creation of unnecessary redirects on Slug changes added
- Sprint Focus deleted (
On Location Sprint)
- Category changed from Site Handling, Site Sets & Routing to Link Handling & Redirect Handling
- Related to Bug #92448: changing slug again after reverting an auto update causes wrong URLs on sub pages added
- Related to Bug #92748: Infinite redirects (redirect loop) when updating slugs added
- Related to Bug #102137: Problems due to automatic redirects added
Also available in: Atom
PDF