Bug #47336
closed
Links between MountPoints
0%
Description
Hi,
I just detected a problem with MountPoints. I have two MountPoints:
http://www.example.de/index.php?id=383&MP=383-2957
http://www.example.de/index.php?id=383&MP=383-4784
and I cannot link from one to the other in my navigation. When I'm in area "4784" and want to switch to area "2957" via navigation, it's still linked to 4784. Same problem in the other direction (from 2957 to 4784), too.
When I'm in a neutral site, both links are working correctly in the navigation.
Updated by Lars Peter Søndergaard over 9 years ago
I have the same issue with TYPO3 6.2.4
After tracking down the Problem in the source, which lies in the typoLink method of the ContentObjectRender class, which calls the method getClosestMPvalueForPage for the page Id and ignores the actual MP that was provided in the URL, I saw that I could disable this behavior by setting the TypoScript option: config.MP_disableTypolinkClosestMPvalue to 1. After that the Problem disappeared.
It still vexes me, so I looked a bit further into the getClosestMPvalueForPage method:
1. getClosestMPvalueForPage takes the current MP value of the current page, if the pageId is the Same. But this doesn't make sense for typoLinks, especially if the mount point is also somewhere else.
2. I think the second case (the nested foreach loops) goes wrong, because it accumulates the current _MP_PARAM values from the current rootline (not the linked rootline).
Updated by Dmitry Dulepov over 7 years ago
- Is Regression set to No
This method also does not work well when the content of the mounted page has to be shown. TYPO3 will try to redirect from the mount point to the mounted page but that function will set MP to the value, which will redirect back to the mount point. Thus endless loop. config.MP_disableTypolinkClosestMPvalue = 1 solves the issue but it is unclear what side effect this will have.
Updated by Benni Mack almost 4 years ago
- Status changed from New to Closed
Agree with Dmitry. We solved this issue in TYPO3 v9.5.17 now properly with site handling, please re-check. Feel free to comment so I will re-open the ticket.