Possibly bug in 1.6.5
Posted: Thu Sep 24, 2009 9:44 am
Hi!
Since upgrading to 1.6.5, the menu system works different, without any notification in the release notes. The CSS classes have been changed, so that the existing menu css won't work anymore (if you used these classes).
The logic has been changed, too:
I got some questions:
- is this documented somewhere? The release notes don't tell about that
- is this a bug or a feature? If the latter: what's the logic behind this? As I see it, this is clearly not a good solution. But I may be missing an important information about the idea behind that.
Cheers,
Alex
Since upgrading to 1.6.5, the menu system works different, without any notification in the release notes. The CSS classes have been changed, so that the existing menu css won't work anymore (if you used these classes).
The logic has been changed, too:
Code: Select all
former version 1.5.x
active page, containing subpages:
<li class="currentpage"><h3><dfn>Current page is 3: </dfn>Testseite</h3></li>
same menu item, after selection of a subpage:
<li class="activeparent"><a class="activeparent" href="http://www.xyz.de/testseite.html"><dfn>3: </dfn>Testseite</a>
--> css classes and coding correctly reflect the state of the menu item
1.6.x
active page, containing subpages:
<li class="menuactive menuparent"><a class="menuactive menuparent" href="http://www.xyz.de/testseite.html"><span>Testseite</span></a></li>
same menu item, after selection of a subpage:
<li class="menuactive menuparent"><a class="menuactive menuparent" href="http://www.xyz.de/testseite.html"><span>Testseite</span></a></li>
--> no change at all, css classes and coding do NOT reflect the state- is this documented somewhere? The release notes don't tell about that
- is this a bug or a feature? If the latter: what's the logic behind this? As I see it, this is clearly not a good solution. But I may be missing an important information about the idea behind that.
Cheers,
Alex