#89916Shortcut to a disabled page with redirect fails
Description
When disabling a page and setting a redirect for that old url to a new/other page, the redirect works.
When setting a page shortcut to the old url, this error shows up:
Page not found: Reason: ID was not an accessible page
Which is obvious because the shortcut functionality checks the availability of the target page.
But maybe it’s wanted/expected behaviour to get redirected if there is a redirect for the page available.
To reproduce:
- Create old-page and set hidden
- Create new-page and set visible
- Create redirect from /old-page to /new-page => this works
- Create shortcut to old-page -> shortcut fails
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
-
[BUGFIX] Shortcut to a disabled page with redirect fails Resolves: #89916 Releases: main
Files 2
History 6
-
Benni Mack commented and changed status
NewClosed <span data-processor="relativetime" data-value="2020-03-26T13:11:08+00:00" > 03/26/20, 13:11 </span> -
Eric Harrer commented and changed attached both-disabled-shortcut-works.png attached only-target-disabled-shortcut-broken.png <span data-processor="relativetime" data-value="2026-01-28T13:00:04+00:00" > 01/28/26, 13:00 </span>
One important aspect of the original ticket is implicit but crucial: the entire scenario assumes a logged-in backend user. Since the target page is disabled, any successful access — whether via redirect, direct access, or shortcut — can only occur in preview context. This is therefore an editorial, not a purely public frontend scenario.
From a technical perspective, the current behavior is understandable. A shortcut resolves its target internally by page ID, and if the target page is not accessible, the resolution fails. This is consistent with the existing implementation.
From an editorial perspective, however, this distinction is difficult to understand and to explain. Editors work with content relationships, not with internal resolution paths.
The observed behavior illustrates this gap:
- A shortcut works when both the shortcut page and the target page are disabled.
both-disabled-shortcut-works.png - A shortcut fails when the shortcut page is visible but the target page is disabled.
only-target-disabled-shortcut-broken.png - Direct access to the disabled target page correctly leads to preview mode.
Technically, the decisive factor is the visibility state of the shortcut page. Editorially, this difference is not meaningful. If an editor has permission to preview a disabled page, it is reasonable to expect the same preview behavior whether the page is accessed directly or via a shortcut.
This is not about changing frontend behavior for anonymous users, but about aligning shortcut handling with existing preview semantics for logged-in backend users to reduce confusion in editorial workflows.
The behavior was analyzed in TYPO3 14.2.0-dev.
- A shortcut works when both the shortcut page and the target page are disabled.
-
Garvin Hicking changed status
ClosedNew <span data-processor="relativetime" data-value="2026-01-28T13:24:09+00:00" > 01/28/26, 13:24 </span> -
Eric Harrer changed target version TYPO3 Version
914 <span data-processor="relativetime" data-value="2026-01-28T13:27:53+00:00" > 01/28/26, 13:27 </span> -
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-03-31T09:05:23+00:00" > 03/31/26, 09:05 </span>
-
Benni Mack changed target version <span data-processor="relativetime" data-value="2026-04-21T11:23:49+00:00" > 04/21/26, 11:23 </span>
Hey Riny.
We’ll the “old-page” is hidden, when someone is pointing to the old-page page ID (which TYPO3 does) then this won’t work obviously. A shortcut is doing an internal resolution and not an external HTTP redirect.
I don’t see this as a bug, but this is expected behavior.
I’m closing this issue, but leave it open for discussion, so you can elaborate if you feel that this is still an issue for you.