Issue Bug Closed

#106740typolinkLinkAccessRestrictedPages with "NONE": wrong url for mount point using access restricted page

Sven Burkert 05/21/25, 11:39 updated 10/26/26, 14:34

Description

Preconditions

TS config

config.typolinkLinkAccessRestrictedPages=NONE

and this page structure:

mount-test
|- page-1 (normal page)
|- page-2 (mount point, uses page-3 as destination)
|- page-3 (normal, access restricted page)

This page structure is also provided in the appended file as T3D import.

Now I’m creating a link on page-1 to page-2.

Result

URL for this link is /mount-test/page-2/mount-test/page-3/
This URL is wrong and resulting in 404 error. When page-3 is not access restricted, it works as expected.

It doesn’t matter if the link on page 1 is in a standard text content element or created by f:link.typolink.
There’s something wrong in method “PageRouter->resolveMountPointParameterIntoPageSlug()“
Error is also occurring in TYPO3 v11.

Reviews 2

Files 1

History 2

  1. Oliver Bartsch commented and changed status New Closed <span data-processor="relativetime" data-value="2026-10-26T14:34:31+00:00" > 10/26/26, 14:34 </span>

    Hey,

    thanks for the detailed report and the T3D, that made it easy to track down.

    The problem is in PageRouter::resolveMountPointParameterIntoPageSlug(). When it builds the URL for a mount point, it loads the mount point page and the mounted page through PageRepository::getPage() with the frontend group access check still on. The target page itself is already loaded with the access check disabled in PageRouter::generateUri(). An anonymous visitor cannot see the access restricted page-3, so its slug comes back empty and nothing is removed from the path. The mount point slug then just gets put in front of the full target slug, which gives you /mount-test/page-2/mount-test/page-3/. With page-3 unrestricted, the prefix is removed correctly and you get /mount-test/page-2/.

    This is the same root cause as #94963 (access restricted mount points in the PageRouter), so I’m closing this one as a duplicate and will continue there.

    Cheers, Oli