Problem/Description¶

Found in TYPO3 11.5.stable:

While working on a "soft"-relaunch I updated a bunch of pages in the page tree. I've used the automatic redirect generation on purpose. Unfortunately also redirects for storage folders were created.

Why got sys folders respected?

Maybe b13/masi has some missing features here and was the main cause for a redirect on a storage folder?! Because of the amount of pages in multiple site page tree's this extension helps a lot. I also had some similar scenarios without "slug-helper-extensions" so far.

Real World Example "News Storage folder":¶

Before moving pages around

After moving pages (of any kind) around

This leads to following redirect:

domain.tld/news → domain.tld/storage/news.

What major drawback does here drops in?¶

Possibility of deleting wrong redirect probably prevented¶

No self-service'sh solution if an limited backend editor has no access to the redirects backend module (even if the person has advanced editor skills)

No table listing in access configuration for redirects¶

For better UX, the sys_redirect tables must not be shown for every backend user. (the sys redirect was created right in the sysfolder /storage/news

A major problem which should be covered: Create a new default page called "News" right under the root page¶

• every request on domain.tld/news gets redirected to domain.tld/storage/news which leads – of course – in a 404
• the editor (also a technically savvy one) gets no info about the hidden gem (redirect)
  • I can't give any project manager, customer the responsibility for checking the response headers for x-redirect-by

General problem on the blue notifications after moving pages¶

The blue notification is somehow hard to understand. I've heard that from many TYPO3 editors already. Maybe one solution is to disable the automatic redirection and instruct editors to create redirects manually – maybe also a good way to make the topic transparent? Who knows...

ToDo(s)¶

Introduce generic "helpers" in the TYPO3 backend to inform every editor about slug-redirect mismatching.

Or do you have some other advices on this topic? Do we have some missing advices in the TYPO3 documentation about the redirect-topic?

I had already some hours invested to discuss some possibilities in the team. But didn't found any working solution for editors.