Issue Feature New Orphaned

#98567Check for redirects without existing target page

Josef Glatz 10/10/22, 15:13 updated 08/02/23, 13:05

Description

Problem/Description

It’s possible that sys_redirect records are getting conflicting when the configured target (like a page with t3://page… schema) is deleted. At least the symfony command `redirects:checkintegrity` reports them.

ToDo(s)

  • Add a schedulable command to check/cleanup such orphaned sys_redirect records

Acceptance Criteria

  • It’s possible to cleanup redirect records in an automatic way if the target isn’t available anymore within the TYPO3 instance.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[FEATURE] Check for redirects without existing target page Resolves: #98567 Releases: main