#99132Redirects module shows redirect from deleted page - not editable not deletable by admin
Description
The Redirects module shows redirects, which reside on deleted pages.
Trying to delete such a redirect simply does nothing.
Trying to edit such a redirect shows an error.
There is not way for an admin/editor to get rid of such a redirect.
(I did not check whether it is still evaluated in FE)
Expected behaviour:- No edit link
- Allow to delete
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 1
History 7
-
Georg Ringer commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2022-11-23T07:10:23+00:00" > 11/23/22, 07:10 </span> -
Markus Klein commented and changed status
Needs FeedbackNew <span data-processor="relativetime" data-value="2022-11-23T08:51:19+00:00" > 11/23/22, 08:51 </span>I’m not sure this is related. The redirect was stored on the correct pid in this case (not pid 0).
-
Andreas Brus commented <span data-processor="relativetime" data-value="2023-01-09T07:07:14+00:00" > 01/09/23, 07:07 </span>
still same Error in Version 11.5.21
Error on trying to edit
no change, no error, no hint on trying to delete -
Markus Klein changed category <span data-processor="relativetime" data-value="2023-11-09T13:10:25+00:00" > 11/09/23, 13:10 </span>
-
Georg Ringer changed Related to #101637 <span data-processor="relativetime" data-value="2025-04-28T19:59:21+00:00" > 04/28/25, 19:59 </span>
-
Michael Stopp commented <span data-processor="relativetime" data-value="2026-09-11T08:04:09+00:00" > 09/11/26, 08:04 </span>
I just noticed that in v13 LTS the behaviour has changed somewhat. At least you get a flash message now:
1: Attempt to delete record “sys_redirect:333” which is not assigned to a valid page
But the redirect still isn’t deleted and it can’t be deleted via the BE module. It seems, if there ever was a good case to delete a redirect record, it would be this, since the redirect has become pointless.
BTW: I noticed that these redirects get deleted by the `redirects:cleanup` console command, though it’s not really clear why from the documentation of the console command.
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-11-04T17:27:01+00:00" > 11/04/26, 17:27 </span>Analysis
This can only happen for redirects which were stored on a regular page. That was the case for a limited period only:
- #91776 (v11.4.0) bound automatically created redirects to the page which triggered them and changed
rootLevelofsys_redirectto-1. - #99044 (v12.1.0) stores automatically created redirects on the root page of the site again. It was not backported to 11.5.
So the maximum affected redirects are automatically created ones from v11.4 up to v12.0, and from all v11.5 releases. Redirects created with v12.1 or newer are not affected anymore.
Redirects created manually in the Redirects module (also short URLs and QR codes) are stored on
pid=0and therefore never reside on a regular page. The table is hidden in the list module, so they cannot be created on arbitrary pages there either.The remaining case mentioned in the first comment, a deleted site root page, is out of scope: such a page is practically never deleted, and the redirects belong to a site which does not exist anymore.
What stays are legacy records created by v11.4 – v12.0 which were never migrated. They are removed by the
redirects:cleanupcommand, so there is a way to get rid of them.Closing as the cause is fixed with #99044.
If this is still valid for you in v14, please open a new issue and provide information how to reproduce it. Thanks!
- #91776 (v11.4.0) bound automatically created redirects to the page which triggered them and changed
this is kind of fixed with #99044 but if the site root page is deleted, the same issue still appears. ideas how so solve or should we close it because the solution of #99044 is fine enough (and site root pages are kind of never deleted ^^?)