Bug #90485

Native URL support for MountPoints doesn't work in multisite environment

Added by Robert von Hackwitz over 1 year ago. Updated over 1 year ago.

Needs Feedback
Should have
Link Handling, Site Handling & Routing
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


We have a multisite environment with dozen of websites.
Each website has a menu generated by TypoScript with PageC as startingpoint
Menu shows correctly on each website frontend, but when a user click ie link generated for Page1 in "Shared Pages" TYPO3 throws sometimes "The requested page does not exist!" and sometimes "id is outside tree root"

Structure is similar to:

TYPO3 Tree |
- siteA.example.com | | | - PageA | - PageB | - PageC (Mount pointing to "Shared Pages") |
- siteB.example.com | | | - PageA | - PageB) | - PageC (Mount pointing to "Shared Pages") |
- Shared Pages |
- Page1
- Page2
- Page3


Updated by Thomas Oliver Moll over 1 year ago

  • PHP Version changed from 7.2 to 7.3

I can confirm this Problem under 9.5.15 PHP 7.3

Apparently this leads to errors:
Id=123 slug=/news -> Normal news page
Id=456 slug=/news -> Doktype Mountpoint pointing to /news(123) within DomainA (same slug diffrent Domain)
Id=457 slug=/test -> Normal Page
Id=789 slug=/test -> Normal Page -> Works fine (No interference with 457)
Id=790 slug=/news -> Normal news page -> Doesn't Work (404 (ID not in Domain))
because resolving /news leads to MountPoint /news(456) from DomainB
which in turn leads to /news(123) from DomainA
and ID=123 is not within DomainC so the the error "ID not in Domain" is triggered
Are mountpoints an legit feature that should work?
Does anyone know about this problem? Why is 456 found when 790 should be found.
changing slug /news to /news-mp at page 456 made 790 work again. But Sites B and C have nothing to do with each other (also A and C)


Updated by Benni Mack over 1 year ago

  • Status changed from New to Needs Feedback

Hey Robert,

can you please check with TYPO3 v9.5.16 as we fixed an issue there regarding this setup?


Updated by Robert von Hackwitz over 1 year ago

Benni Mack wrote:

Hey Robert,

can you please check with TYPO3 v9.5.16 as we fixed an issue there regarding this setup?

Hi Benni,
unfortunately not. It still doesn't work

Also available in: Atom PDF