-
- 83 Posts
If I use [!DropMenu!], I get:
<li class="here">Home</li>
Now, if I change to [!DropMenu? &selfAsLink=`true`!], I get:
<li><a href="index.php?id=1" title="Introduction to MODx">Home</a></li>
Here class has disapeared.
Are selfAsLink and hereClass compatible?
at the edge of dawn,
you ask yourself if your shadow did follow you down
all night long
They should be... please file a bug report. Thanks!
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
This has been brought up repeatedly; I’ve been using a hacked version to deal with this since it was first released.
http://modxcms.com/forums/index.php/topic,2609.msg17880.html#msg17880
LOL... a good reason to make sure it’s in the bugtracker!
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
hm, I just always presumed that you and Jason wanted it that way for some reason.
-
- 20 Posts
there is the same problem with the dropmenu Lammikko hack :
http://modxcms.com/forums/index.php/topic,3996.0.html
i have tested it !!
-
- 20 Posts
Quote from: dernier_recours at Apr 19, 2006, 12:56 AM
Here class has disapeared.
i was going wrong, "here" class does not disapear. You just have to add another CSS rule :
li.here, li.here a {.......}
when setAsLink is enable , the "title link" would have to be styled like the li.here {....}, for having the same visual effect.
This doesn’t work too well if you’re making a menu using CSS backgrounds and borders for a multilevel menu; you need to be able to style the li.here with a background, but now this will also affect the submenu that is now opened. And it also kills any "sliding-doors" image backgrounds you are using.
-
- 20 Posts
@susan
yes , i know, but this is a CSS problem
i reply to the first post: class "here" doesn’t desapear when using the setAsLink=true parameter
++