DropMenu's problem

[Guest]

Welcome, Guest. Please login or register.
Did you miss your activation email?

1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[openagate]

The Problem of such plan:

I want to use the DropMenu several times on one page in different places. Herewith in each event with different input: maxlevels and startdoc.

But there is determined restrictions for the request to database.

Is there some way to cause the DropMenu only once? And in rest events to work with an array which already got by DropMenu.

[rthrash]

Currently, that is not possible. Sorry!

[openagate]

Thanx for a sorry...

Sadness has stolen a quietness from my heart:(

hope, this problem will be solved in the future;)

[Kunal Kapoor]

I found another little issue but isn't really major:

If you were to call the dropmenu snippet, and select &selfAsLink=`0` and hereClass=`current`, this works fine. However, if you had &selfAsLink=`1`, &hereClass=`current` no longer works.

Like I said, it wasn't a major issue! 

[sottwell]

If you're using the sliding-doors tab image technique, it is a big problem.  You need both the li and the a elements for styling, plus you need the "here" class for styling the current link.  I fixed it (sort of...) by changing line 259

Code:

if ($itm && !$selfAsLink && ($child['id'] == $modx->documentIdentifier)) {

to

Code:

if ($itm && ($child['id'] == $modx->documentIdentifier)) {

This way it outputs the "here" class whether it's a link or not.  Now both can be styled nicely using the sliding-doors technique.  I'm not sure how this will affect nested links; I'm only using it to style single-level horizontal tab style menus.

[Kunal Kapoor]

Thanks for that. Works a treat! 

[mikedfunk]

Thank you, I was having this exact problem. I wanted the link to be styled as an active tab and this would have been a pain without an a element. Many thanks!

[MadeMyDay]

lol, I should read the forum first

Just posted it here:

http://modxcms.com/bugs/task/323

Marc

[davidm]

If you're using the sliding-doors tab image technique, it is a big problem.  You need both the li and the a elements for styling, plus you need the "here" class for styling the current link.  I fixed it (sort of...) by changing line 259 (...) This way it outputs the "here" class whether it's a link or not.  Now both can be styled nicely using the sliding-doors technique.  I'm not sure how this will affect nested links; I'm only using it to style single-level horizontal tab style menus. 

Thanks a LOT Susan for the fix !

I was going crazy with this...
I'll soon report about the nested links, since I have been having a big problem to have a 3-level menu working as expected...

Edit : It works A-OK with my 3-level menu
I wish I had seen this thread before losing a few hours over this

[The Man Can!]

Thanks a LOT Susan for the fix !

Ditto on that, Susan. Sliding doors working like a charm now.