Project

General

Profile

Actions
Copy link

Bug #22130

closed

Nested mountpoints result in broken typolinks in the FE

Added by Anonymous almost 15 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2010-02-17
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
5.2
Tags:
Complexity:
hard
Is Regression:
No
Sprint Focus:

Description

Scenario:
Mountpoint A points to a page B that contains mointpoints (C and D) to other pages itself.

Visiting A in the FE generates correct typolinks for C and D (with all the needed IDs in the MP parameter), but visiting C (via A not via B) creates a correct typolink for C but not for D.

The typolink for D (when visiting C via A) contains a MP parameter that doesn't contain the last chain of that MP chain, that should be something like MP=B-A,X-D. X being that page that is being mounted in D.

Hope it's not too confusing and has not been reported before, I most centainly did search on that.

(issue imported from #M13562)

Files

T3D__2013-09-27_13-50.t3d (16 KB) T3D__2013-09-27_13-50.t3d Anonymous, 2013-09-27 13:52

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Bug #29584: Shortcut to mountpoint results in illegal root treeRejected2011-09-09

Actions
Actions
Copy link
 #1

Updated by Alexander Opitz about 11 years ago

  • Category deleted (Communication)
  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions
Copy link
 #2

Updated by Alexander Opitz about 11 years ago

Beside of that outdate, does #29584 helps?

Actions
Copy link
 #3

Updated by Anonymous about 11 years ago

Wow, that's been quite a while ago ;-)

But yes, problem still exists in 4.5 and 6.2-dev.

Attached you'll find the page structure I just used when trying to reproduce this behaviour.

Actions
Copy link
 #4

Updated by Anonymous about 11 years ago

And no, the patch you mentioned didn't solve this problem.

Actions
Copy link
 #5

Updated by Alexander Opitz almost 11 years ago

  • Status changed from Needs Feedback to New
Actions
Copy link
 #6

Updated by Mathias Schreiber almost 10 years ago

  • Target version set to 7.2 (Frontend)
  • Complexity set to hard
Actions
Copy link
 #7

Updated by Benni Mack over 9 years ago

  • Target version changed from 7.2 (Frontend) to 7.4 (Backend)
Actions
Copy link
 #8

Updated by Susanne Moog over 9 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions
Copy link
 #9

Updated by Benni Mack about 9 years ago

  • Target version changed from 7.5 to 7 LTS
Actions
Copy link
 #10

Updated by Mathias Schreiber about 9 years ago

  • Target version deleted (7 LTS)
Actions
Copy link
 #11

Updated by Riccardo De Contardi almost 9 years ago

  • Category set to Frontend
Actions
Copy link
 #12

Updated by Benni Mack almost 5 years ago

  • Status changed from New to Closed

hey philipp,

I've reproduced this and it works for me in TYPO3 v8, v9 and v10. I will close this issue now. Please let me know if you feel otherwise, so I can re-open the ticket.

Actions
Copy link

Also available in: Atom PDF