ActiveMenu compatibility with certain themes

The way i re-engineered the menu system was so that all menu items were the full width of the menu, regardless of indentation. This allowed for the alternating row colors, full block links etc.

I cannot see how to change the icon to be set as a background image and still be clickable. There is a garland.css in the theme folder in the activemenu module folder. If you rename that to framework.css and upload it to the same location, you can see how it could work, but the + and - icons are no longer clickable.

adding a framework.css (copy from garland.css) in activemenu/theme only partially solve the issue. The active menu features collapse/uncollape is now gone. bTW, the + and - is clikable.

however, "ArtistsC01" is doing perfectly handling this issue without putting anything in the activemenu/theme ?

anyone care to re-engineer ...

Here is as far as I got with it. The styling is about right, but only the current active menu functions properly. And something looks kinda weird in IE7.

Make this a framework.css in the activemenu theme folder.

subscribe. I have Activemenu running, but the +/- appears in its own column to the left of the menu items, and because it's in its own column, it does not indent--just a vertical column.

This is a great theme, by the way.

Update version.

Updating version.

And changed to a bug since this affects out-of-the-box functionality. If it's an Activemenu bug, this should be transferred.

Changing to critical because it significantly impacts use of the theme.

A supplementary menu utility module not being supported "significantly impacts the use of the theme"? That's rather excessive. I think I'll keep it at the priority level I had it set at before, if that's ok with you...

If no one else takes a shot at fixing this, I'll revert the menu system to the "garland" style, which would possibly remove the zebra striping and full width block links features from the next Framework release.

I'll review this issue to try to build the menu in a format favored by this module, while keeping the visual format of the menu the same.

I hope to resolve this in release 2.1.

legacy menu/list support is now included in the 2.1 CSS file. Directions are given to comment out default list/menu/zebra coloring, then just uncomment the legacy list/menu code.

Still not working. +/- are appearing on the left hand side in their own column.

It appears you enable legacy list support. For Framework 6.x-2.1, please see line 532 in style.css

It involves a simple uncommenting and commenting out of code.

I realize that this may be an unintuitive solution, but it is a compromise for those who want the more fully supported, zebra colored lists, or the legacy lists that is required by some modules.

Here is an example of how you could comment the code. The following is commented for legacy support.

/* lists /
dl { margin: .5em 0 1em; padding: 0; }
dl dd { margin: 0 0 .5em 1.5em; }
ol { margin: .5em 0 1em; padding: 0 0 0 1.5em; }
ol li { margin: .15em 0 .15em .5em; padding: 0 0 .2em; }
ol ul li { margin-left: .5em; padding: 0 0 .2em 1.5em; }
ul { margin: .5em 0 1em; padding: 0; }
.item-list ul { margin: .35em 0 0 -.5em; padding: 0; }
.item-list ul ul { margin-left: 0; }
ul li, ul li.leaf, .item-list ul li { background: transparent url(images/menu-leaf.gif) no-repeat 1px .35em; list-style-image: none; list-style-type: none; margin: .15em 0 .15em .5em; padding: 0 0 .2em 1.5em; }
ul li.expanded { background: transparent url(images/menu-expanded.gif) no-repeat 1px .35em; }
ul li.collapsed { background: transparent url(images/menu-collapsed.gif) no-repeat 0 .35em; }
ul li.leaf a, ul li.expanded a, ul li.collapsed a { display: block; }
ul.inline li { background: none; margin: 0; padding: 0 1em 0 0; }
ul ol li { background: none; list-style-type: decimal; margin-left: 2em; padding: 0 0 .2em; }
ul ul li { margin-left: 2em; }

/* menu /
ul.menu { margin: 0; padding: 0; }
ul.menu li { background-position: .3em .6em; list-style-image: none; list-style-type: none; margin: 0; padding: .1em 0 .1em 0; }
ul.menu li a { padding: .1em 0 .1em 1.5em; }
ul.menu li ul li { background-position: 1.5em .6em; }
ul.menu li ul li a { padding-left: 2.7em; }
ul.menu li ul li ul li { background-position: 2.7em .6em; }
ul.menu li ul li ul li a { padding-left: 3.9em; }
ul.menu li ul li ul li ul li { background-position: 3.9em .6em; }
ul.menu li ul li ul li ul li a { padding-left: 5.1em; }
ul.menu li.expanded { padding-bottom: 0; }
ul.menu li.expanded ul { margin-top: .1em; }

/* menu zebra coloring /
ul.menu li { border-bottom: 1px solid #d4e7f3; padding: .2em 0 .2em 0; }
ul.menu li a { padding: .2em 0 .2em 1.5em; }
ul.menu li.odd { background-color: #fff; }
ul.menu li.even { background-color: #edf5fa; }
ul.menu li.expanded { background-color: #d4e7f3; border: none; padding-bottom: 0; }
ul.menu li.expanded ul { border-bottom: 3px solid #d4e7f3; border-top: 1px solid #b4d7f0; margin-top: .2em; }
*/

/* legacy list support -- MUST COMMENT OUT [LISTS/MENU/ZEBRA COLORING] ABOVE -- remove brackets around asterisk to enable -- */
ul { margin: .5em 0 1em; padding: 0; }
ol { margin: .75em 0 1.25em; padding: 0; }
ol li, ul li { margin: .4em 0 .4em .5em; }
ul.menu, .item-list ul { margin: .35em 0 0 -.5em; padding:0; }
ul.menu ul, .item-list ul ul { margin-left: 0; }
ol li, ul li, ul.menu li, .item-list ul li, li.leaf { margin: .15em 0 .15em .5em; }
ul li, ul.menu li, .item-list ul li, li.leaf { background: transparent url(images/menu-leaf.gif) no-repeat 1px .35em; list-style-image: none; list-style-type: none; padding: 0 0 .2em 1.5em; }
ol li { margin-left: 2em; padding: 0 0 .3em; }
ul li.expanded { background: transparent url(images/menu-expanded.gif) no-repeat 1px .35em; }
ul li.collapsed { background: transparent url(images/menu-collapsed.gif) no-repeat 0 .35em; }
ul li.leaf a, ul li.expanded a, ul li.collapsed a { display: block; }
ul.inline li { background: none; margin: 0; padding: 0 1em 0 0; }
dl { margin: .5em 0 1em 1.5em; }
dl dd { margin: 0 0 .5em 1.5em; }
/* end legacy list support */

Sorry, upon further inspection, an activemenu theme needs created.

Create a file called framework.css and place in into the "..modules/activemenu/theme" directory.

Confirmed fix: Enable Legacy support in style.css and create the framework.css as noted above.

Thanks.

I see the thing about legacy support. Does this mean that ActiveMenu needs to be updated? Or does this mean that Framework is shipped in a weird mode?

In other words, why is this not a theme bug?

I completely rebuilt the way the ordered and unordered lists were formatted, allowing for better support of lists within lists (ex: ordered within an unordered and vice versa) as well as allowing the coloring of the links (in this case, the zebra coloring).

The reason background coloring would not look good in the "legacy" mode, is that each sub-link is indented, making each link a different width. The default Framework sub-links just have the appearance of indention, achieved through left padding instead of margin, allowing for the entire width of the links to remain constant to make for a good looking styled list.

This is not a bug, it is a design choice. Now that both formats are supported, there should be no problems. There are only a few cases, as with activemenu, that legacy lists should be required due to that module being designed for a certain list format.

Framework with legacy support turned on requires the same theme file for activemenu that Garland does. If you wanted, you could rename garland.css found within "..modules/activemenu/theme" to framework.css, and it would work.

If I found that no one cares about more complex combinations of list support and coloring options, I would scrap the code and ship it in "legacy" mode by default.

I feel I've explained quite enough on this issue, and since it can be put in working order with little effort out of the box, I consider this issue FIXED.

Thanks for your interest Aren and being patient with this issue. I hope you understand why things are the way they are.

Thank you. That's fine. I'm just trying to discern if there is room for improvement in the ActiveMenu module.

I have transferred this as a feature request to ActiveMenu to see if they have any thoughts on improvement for ActiveMenu.

Renaming title to be appropriate for ActiveMenu support queue.

I'd welcome patches to improve activemenu theme compatibility.