Project

General

Profile

Actions

Bug #24367

closed

changes in tmenu_layers.php broke TMENU

Added by Daniel Wagner over 13 years ago. Updated over 10 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2010-12-19
Due date:
% Done:

0%

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

Description

submenues appeared on mouseover (sometimes at wrong places) but often never disappeared.
update from 4.2.15 to 4.2.16 changed the creation of the unique menu id. maybe it's not unique anymore.
replaced (t|g)menu_layers.php by the old versions and now everything works fine.

(issue imported from #M16783)


Related issues 3 (0 open3 closed)

Related to TYPO3 Core - Bug #21388: typo3temp got filled with thousands of javascript_* filesRejected2009-10-28

Actions
Related to TYPO3 Core - Bug #23866: layered menus generate "too much recursion javascript-error"Rejected2010-10-28

Actions
Has duplicate TYPO3 Core - Bug #28640: TMENU_LAYERS does not always create unique IDs for the third levelRejected2011-08-01

Actions
Actions #1

Updated by Daniel Wagner over 13 years ago

there should be better way to solve this problem: set a layer_menu_id in TMENU
(see http://bugs.typo3.org/view.php?id=12376)

but this does not solve my problem. getting a javascript error because
array GLV_menuXY does not contain needed entry when called by GL..._doTop.

Actions #2

Updated by Helmut Hummel over 13 years ago

@wagner could you post your TypoScript that fails with the current version?

Actions #3

Updated by Torben Hansen over 13 years ago

I can confirm this bug. Menuitems are not unique anymore. See bugreport 0016165

Actions #4

Updated by Christian Hernmarck about 13 years ago

I confirm this bug.
If reverting bug 12376 then it works:
since 4.2.16:
  1. $this->WMid = trim($this->mconf['layer_menu_id']) ? trim($this->mconf['layer_menu_id']) . 'x' : substr(md5('gl' . serialize($this->mconf)), 0, 6);
    till 4.2.15:
    $this->WMid = trim($this->mconf['layer_menu_id'])?trim($this->mconf['layer_menu_id']).'x':substr(md5(microtime()),0,6);

my (shorted) typoscript:

temp.navtext {
entryLevel = 0
1 = TMENU_LAYERS
1 {
noBlur = 1
wrap = &lt;ul class=&quot;level1&quot;&gt;|< /ul>
expAll = 1
layerStyle = position:absolute;visibility:hidden;
lockPosition = y
hideMenuWhenNotOver = 1
hideMenuTimer = 250
leftOffset = 20
topOffset = 40
relativeToTriggerItem = 1
NO{
allWrap = &lt;li class=&quot;no&quot;&gt;|< /li>
}
}
2 < .1
2 {
wrap = &lt;ul class=&quot;level2&quot;&gt;|< /ul>
leftOffset = 200
topOffset = 5
xPosOffset = 0
yPosOffset = 0
relativeToTriggerItem = 1
relativeToParentLayer = 1
}
3 < .1
3 = TMENU
3.wrap = &lt;ul class=&quot;level3&quot;&gt;|< /ul>
}

Problem: the 3rd layer on first position is always the same, and the 2nd position on the 3rd layer always the same (from first occurence)... etc.

I cannot set different layer_menu_id for the different LEVEL2-Menus.... - this would maybe fix it also....

Actions #5

Updated by Simplicity GmbH about 13 years ago

I can confirm this bug too. After an update from 4.4.3 to 4.4.6.

Replace the tmenu_layers.php file with the old one and it works again.

The fix for bug 0012376 seems to have introduced the problem.

Actions #6

Updated by Christian Hernmarck about 12 years ago

  • Target version deleted (0)

What about this issue?
Just saw that we still have the false behavior in 4.5.11: a broken menu in the 3rd level:

Main1 | Main2 | Main3
Sec1
Sec2
Sec3 > Thrd1
Sec4 Thrd2
Thrd3

The the third menu is often the same and some of them are placed in the upper left corner. That's because some of the menu-div have the same id...
With my change (see Comment 4 above) it's ok.

What is needed to go on with this?

/Christian

Actions #7

Updated by Christian Kuhn about 11 years ago

  • Category deleted (Communication)
  • Status changed from New to Rejected

With 6.1 issue #46358, the _layers menus where moved to statictemplates, and statictemplates was removed from core afterwards. This issue won't be solved in the core anymore.

Actions

Also available in: Atom PDF