Bug #20662
closed<link> & mount points & cross domain & typolinkCheckRootline = broken
0%
Description
I have two websites, one is the master (A) and one is using mount points (B).
On A is a page (A1) which has two links to another page in A, not a sub page, but somewhere else in the tree (A2). The first link (L1) is done as content element menu of pages, the second link (L2) is done through <link>.
On website B I have a mount point the includes A1 (=B1) and somewhere else I have a mount point which includes A2 (=B2).
I have "config.MP_mapRootPoints = root" set to have those different mount points found. This works, both links L1 & L2 are pointing to the corrent domain B page with MP added and so on.
Now I removed the mount point to B2 - say this page is not existing in website B. What happens is that both links point to website B with the page ID of A2, but without the MP parameter.
Okay, that's what "config.typolinkCheckRootline" is for, right? Okay, A1 is mounted as B1 and A2 is NOT mounted. Both links now point to domain A without the MP parameter. That's correct, since it should be handled as an external link if the page is not existing.
If I now re-mount A2 as B2 the links should change to domain B with the correct MP parameter, right? Well L1, the menu element link is doing so, but t L2, the <link> one, is still pointing to domain A with the page ID of A1 and without MP parameters.
This is happening when using multiple mount points, but hey, this is the normal thing here. Links from A1 to A1.1 are correctly set to domain B with page id of A1.1 and MP parameters on both link types.
So it seams that "config.typolinkCheckRootline" is somehow overriding the "config.MP_mapRootPoints = root" setting or check when using multiple mount points.
(issue imported from #M11398)
Updated by Alexander Opitz over 11 years ago
- Category deleted (
Communication) - Status changed from New to Needs Feedback
- Target version deleted (
0)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
- Is Regression set to No
No feedback for over 90 days.