Issue Bug Closed

#47336Links between MountPoints

Albrecht Köhnlein 04/18/13, 09:57 updated 05/19/20, 19:03

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.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 3

  1. Lars Peter Søndergaard commented 09/22/14, 11:52

    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).

  2. Dmitry Dulepov commented and changed Is Regression 0 09/20/16, 13:12

    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.

  3. Benni Mack commented and changed status New Closed 05/19/20, 19:03

    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.