[straygoat]

Hi Admin,

I still have a couple of issues.

When I have a level 3 sub menu (so that’s menu>sub-menu>sub-menu), the level 3 menu doesn’t expand automatically, only level 1 and level 2 do.

Also, is there a way to get only the lowest level currently selected page to be highlighted in the menu? At the moment, if I select a level 3 menu, it highlights the level 1, level 2, and level 3 menu options.

[straygoat]

Hi admin and everyone else.

I have just tried the solution posted and can confirm it works when used with MadCap Flare. Thanks a lot.

[straygoat]

Thanks. I will give it a go later this week and see how it works. Yes, it was just the expanding menus issue that was a problem. Oh, and the menu appearing without formatting (FOUC) when the page first loads, but I think setting ‘display’ in the css can cure that.

I’ve since found another way of doing it with foundation menus, but it is good to have the smartmenus solution too, as your solution allows the top-level menu items to link to content as well.

[straygoat]

I have put a small sample project up here:

http://straygoat-technicalauthor.co.uk/smartmenutest/TestingMenuFix/Content/Doors.htm

I’ll explain what is in place:

Everything in the page is created in MadCap Flare, which lets us create topic htm files, a toc file, and associate them with a skin. The skin uses Foundation, and if you reduce the browser size, you will see that eventually, a hamburger icon appears and this brings in a slide-in menu (this is a Foundation menu).

Everything above the search bar is defined in the skin, and everything from the space bar down is laid out using a master page and CSS. In the master page, I have used a menu proxy which provides Flare’s table of contents as a regular ul, li list. With a little help from a script and an XSLT transform (both supplied by someone else), the menu proxy is converted into a list that will work with smartmenus.

The main content is loaded in from the htm topics I create in Flare and the footer is just some images I added in a div at the bottom of the master page.

If you experiment with the Doors menu and its sub-menus, you will see that the expand doesn’t work right.

I suspect the problem with the expand is some sort of clash with the foundation menu. It only seems to occur when the skin is used (it is possible to create the project without a skin, but I need to keep that in place for the foundation menu). I was unaware of the problem occurring when the topic contains a link elsewhere, but have added links to the topics just in case.

Maybe someone can shed some light on what is going wrong?

[straygoat]

lhguillory-flare – I think we need to get a sample up so that people can see what is going on.

[straygoat]

After some investigation over the weekend, I discovered that the smartmenu only stops working when the MadCap output uses a ‘skin’. So there must be a conflict with the skin and the expand/collapse script. I can’t post the URL because of client confidentiality, but I will try and make a blank project that has the same issue.

[Author]

Posts