This project is read-only.


Problem with 4 level menu in Tidy


Adam, in my production site I have a menu which is 4 levels deep. While testing Tidy on my development machine the levels lower than second level are invisible probably due to this css entry of:
#dnnMenu .subLevel .subLevelRight ul {
     display: none;
Changing the value to e.g. block shows the lower level of menu but of course it stays put all the time.

Have you checked Tidy in multiple menu levels environment? Don't want to sound too demanding here but I'm in the final stages of applying Tidy to my production site and any prompt idea would be extremely welcome.

I thought of manipulating the tidy.js myself but when browsed the threads here and here I realized that you mentioned fixing the bugs in the next release so maybe all fixes would be incorporated there.

Any news on the next release, Adam? :)
Closed Jul 13, 2014 at 9:17 PM by adamhumphrey
Version 1.2.0 added 4 levels of sub-menu flyouts.


adamhumphrey wrote Mar 18, 2014 at 5:18 PM

Hi Greg,

Yes, there has been more than enough requests to support sub-menu, sub-sub-menu, etc. flyouts in Tidy. It is definitely a feature I will review for the next release.

Sorry, but I don't have a firm date for the next release. But I'm certain there will be a major update by mid-year.

adamhumphrey wrote Jul 13, 2014 at 9:16 PM

Hi Greg,

Version 1.2.0 added sub-menus. Give it a shot and let me know how it works for you.

Greg_Greensky wrote Jul 14, 2014 at 6:12 PM

Thanks Adam for the follow-up. However, in the meantime I modified your skin on my own so it had the four-level fly-outs as early as in May. It can be seen in action at

Unfortunately I cannot test your new version as "mine" (meaning your older version modified by me) interferes with your install.

As soon as I get to grips with this I'll let you know my observations.

Yet I peeked into two of the files I found to have the major impact on the skin menu: ULtokens.txt and tidy.js. "Mine" are tweaked but I'm not sure if I didn't overdo them too much.

Anyway I'll come back to you when I'm done with the install of the 1.2.0.