Actualy I only want to write that the actual s9y menu-list has a structural error:
Code: Select all
<ul class="serendipitySideBarMenu serendipitySideBarMenuEntry">
<li class="serendipitySideBarMenuHead serendipitySideBarMenuEntryLinks">Einträge</li>
<li class="serendipitySideBarMenuLink serendipitySideBarMenuEntryLinks"><a href="serendipity_admin.php?serendipity[adminModule]=entries&serendipity[adminAction]=new">Neuer Eintrag</a></li>
<li class="serendipitySideBarMenuLink serendipitySideBarMenuEntryLinks"><a href="serendipity_admin.php?serendipity[adminModule]=entries&serendipity[adminAction]=editSelect">Einträge bearbeiten</a></li>
<li class="serendipitySideBarMenuLink serendipitySideBarMenuEntryLinks"><a href="serendipity_admin.php?serendipity[adminModule]=comments">Kommentare</a></li>
or as simple structur:
Code: Select all
<ul>
<li class="serendipitySideBarMenuHead>Entries</li>
<li>new entry</li>
<li>edit entries</li>
...
this ul-structure suggest that all these three points are on the same level. The statement ""Entries" is the top-item, the other are sub-items" is only given by the class of the first li.
strucural better:
Code: Select all
<ul>
<li>Entries
<ul>
<li>new entry</li>
<li>edit entries</li>
</ul>
</li>
<li>next top item - eg. media
<ul>
<li>add medai</li>
<li>library</li>
</ul>
</li>
...
then the logical strucure is be reflected in the html-structure.
So, now I see that my find makes a structical error, too.
Every top-item is its own <ul>-Element! (s9y does this error, too)
But the whole menu is - logicaly - a single list of top and nestes sub-items!
I try to adopt the founded code now.