Bug #21832
closed
HMENU does not generate correct links for mount points with "substitute mount point"
0%
Description
In this Mount Point Scenario:
+ Start
- Page A- Page A1 [2180] Mount Point A1a --> 2051
--
- SysFolder B- [2051] Page B1-- Page B1a
Page A1a (id=2180) is set as a Mount Point which points to Page B1 (id=2051).
Checkbox "Substitute Mount Point (this page) with Mounted page" is set.
The correct address for the page A1a is now
index.php?id=2051&MP=2051-2180
displaying the contents of B12051 in the rootline of A1a2180
However, HMENU with special=directory of subpages for Page A1
produces this address
index.php?id=2180
Calling this address of course produces this error:
"The requested page didn't have a proper connection to the tree-root!
(Illegal Mount Point found in rootline)"
HMENU works fine when the correct address
index.php?id=2051&MP=2051-2180
is being called explicitely and when subpages of Page B1 are generated.
Going up the rootline to Page A1, displaying its subpages, reproduces the bug.
I am not sure if this is a TemplaVoila issue. The bug appeared in a TemplaVoila environment.
(issue imported from #M12995)
Files
Updated by Tolleiv Nietsch over 14 years ago
HMENU is not affected by TemplaVoila and it's part of the Core therefore I'll move the issue into the "Core" project...
Updated by Benni Mack over 14 years ago
hey volkmar,
are you using TMENU, GMENU or JSMENU? Can you post your TypoScript snippet?
Updated by Volkmar Lecke over 14 years ago
Hey Benjamin,
thanks for your reply. It's a GMENU in my case, and it's pretty hard to reproduce, I have to admit. I found out that its occurence depends on the rootline level you are in. It occurs when the mount point is a subpage of the currently shown page.
In contradiction to my first description THE SPECIAL PROPERTY IS NOT SET. It's not special=directory.
To cut a long story short, I fixed the issue by editing class.tslib_menu.php, at least for my purposes it's working, though it's not really the elegant way to substitute mountpoints.
The attached file is that quick and dirty bugfix. My intention is to show you, where in the core code the problem should be fixed. If someone uses it to fix the problem in their installation, please note that the title of the MP is not substituted.
Updated by Alexander Opitz almost 11 years ago
- 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 Volkmar Lecke almost 11 years ago
Alexander Opitz wrote:
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Yes, the issue is still present in TYPO3 4.5. Haven't tested it in v6.
Updated by Riccardo De Contardi almost 11 years ago
I've done the following test in TYPO3 CMS 6.1; I use fluid as template engine instead of Templavoilà.
Pagetree:
Home[ID=1]
|
+-A1[ID=37]
| |
| +-suba1[ID=39]
| +-suba2[ID=40]
| +-suba3[ID=41]
|
+-Some page[ID=4]
|
+-some other page[ID=9]
|
+-B1[ID=38]
A1 is configured as Mount point with the following options:
1. Mounted page:B1
2. Show content from: mounted page
I can't see the checkbox "Substitute Mount Point (this page) with Mounted page"...:S ??
Now with this configuration the page "B1" is shown as 1st level page instead of A1, and its URL is
/index.php?id=38&MP=38-37and shows the content of B1.
in Home page, I create a CE, type: special menus, subtype: menu of subpages of selected pages.
as "Selected Pages" I choose A1.
Home page> the menu is empty.
Then I add some subpages to B1:
B1[ID=38] +-subb1[ID=42] +-subb2[ID=43]
Now the menu in home page shows subb1 and subb2, and their links are:
index.php?id=42&MP=38-37 index.php?id=43&MP=38-37
They act as 2nd level pages
Is this sufficient or is there something I've missed?
Updated by Alexander Opitz almost 11 years ago
- Status changed from Needs Feedback to New
Updated by Mathias Schreiber over 9 years ago
- Target version set to 7.2 (Frontend)
- Is Regression set to No
Updated by Volkmar Lecke about 9 years ago
After an update to TYPO3 v 6.2, the error does not occur anymore.
Issue may be closed.
Updated by Riccardo De Contardi almost 9 years ago
- Status changed from New to Closed
Closed on request of the reporter.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.