Invalid Redirect Validation
Prevent users from adding URL redirects which do not create valid pages on platformOS.
This has the benefit of not creating a false sense of security that redirect works and also avoids an issue where the site cannot be pulled to a windows machine in CLI (?) not valid in windows file names.
Log in to comment and vote
Comments3
Matt Jones
Jul 30
Additionally, we need to warn users in the following situation:
They have an existing page at /x/y, but no legitimate page at /x
They have out of date links going to /x
They create a redirect from /x=> /z
They need to be aware that this can prevent users accessing the legitimate page at /x/y using standard redirects.
Even better than a warning, we can potentially set an appropriate max_deep_level on the redirect to stop it from overwriting existing deeper pages. This could be a much more user-friendly solution if it works.
Matt Jones
Sep 17, 2025
Since the original task was made, CLI can now pull sites like this, since it ignores invalid redirects. However, it would be better if people had feedback if their redirect is not valid, as they would have written it for a reason and if it’s not working they need to know to use other methods.
Matt Jones
Sep 17, 2025
Also, I believe it is possible to write a redirect which breaks a category detail page.
E.g. if you have a category with slug a and a child category with slug b. Maybe category a is not set to detail page, but category b does have detail page turned on.
Setting a redirect from /a to /c breaks the category detail page at /a/b without warning.