Bug #86331

Mountpoints not working with new site configurations

Added by Alexander Grein about 3 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Start date:
2018-09-20
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:
On Location Sprint

Description

To reproduce:

Add two root pages with a site configuration for each.

Add a standard page with the name "page1" to site a.

Add a mountpoint page with the same name to site b.

Try to open page1 of site b in a browser: e.g. www.site-b.com/page1

Expected:
A page containing the same content as www.site-a.com/page1

Result:
A automatic redirect to a page with a url like www.site-*a*.com/page1?MP=3-20 showing an error:
PageNotFoundException: ID was outside the domain

The menu provider also generates wrong links to the site a with additional MP parameter.


Related issues

Related to TYPO3 Core - Bug #89039: MointPoints result in 404 if mounted page is outside the SiteClosed2019-08-29

Actions
Related to TYPO3 Core - Bug #82521: Links to a mounted page in a page tree with a different domain are not prepended with the domainClosed2017-09-20

Actions
Related to TYPO3 Core - Bug #90156: Avoid removing empty prefixes in mount-point handlingClosed2020-01-20

Actions
Related to TYPO3 Core - Bug #90166: MountPoints with Site Handling crash if two sites have a page with the same slugClosedBenni Mack2020-01-21

Actions
Related to TYPO3 Core - Bug #90648: Infinite recursion with new mount point support in sites with multiple websites with same slug name for mount pointsNew2020-03-05

Actions
Related to TYPO3 Core - Bug #90469: Mountpoint information fetched for slug outside of site rootClosedPatrick Broens2020-02-21

Actions

Also available in: Atom PDF