Odd navigator problem preventing site going live
Permalink
Hi
I have a site that is ready to go live, except for one strangeness with the top-level navigator and I'm hoping somebody can help.
The site in question can be found athttp://www.lbdscouts.org.uk/conc...
If you hover over the main navigator, which uses superfish to animate it, the drop downs all work OK, except for that under "Contact Us". There are no sub-pages under this page, but a whole lot of pages appear.
The sub-pages are actually under two hidden top level pages that are not included in the navigator selection. All sub-pages have the property "Exclude from Nav".
The navigator uses the code:
Any ideas?
Gareth
I have a site that is ready to go live, except for one strangeness with the top-level navigator and I'm hoping somebody can help.
The site in question can be found athttp://www.lbdscouts.org.uk/conc...
If you hover over the main navigator, which uses superfish to animate it, the drop downs all work OK, except for that under "Contact Us". There are no sub-pages under this page, but a whole lot of pages appear.
The sub-pages are actually under two hidden top level pages that are not included in the navigator selection. All sub-pages have the property "Exclude from Nav".
The navigator uses the code:
$bt = BlockType::getByHandle('autonav'); $bt->controller->displayPages = 'top'; $bt->controller->orderBy = 'display_asc'; $bt->controller->displaySubPages = 'all'; $bt->controller->displaySubPageLevels = 'custom'; $bt->controller->displaySubPageLevelsNum = '3'; $bt->render('templates/header_menu_dropdown');
Any ideas?
Gareth
http://www.concrete5.org/marketplace/addons/autonav-exclude-subpage...
...but since you already have your own custom template for the menu, it is not going to be straightforward to integrate this. Your best bet would be to use the Autonav Exclude Subpages template and re-apply your superfish css to that (as opposed to trying to bring in the Autonav Exclude Subpages functionality to your existing superfish template).
Or maybe you can upgrade the site to 5.6 which should solve this problem for you (although it may cause other problems... especially if you're on 5.4 -- it's *very* different).