Posted 26 May 2013 - 03:55 PM
I just upgraded to Pagelines 2.4.2 from PlatformPro 1.6. I changed my menus to the new Fixed NavBar which works great except for one issue...the top level of my dropdown menus no longer works (if any of them have submenus). I have the top menu configured to go to a landing page on some of them and then subbmenus underneath to go directly to areas within that heading. However, when I hover over the top levels that have the submenus, instead of showing the actual configured link, they show, , etc. The submenus show the actual links and are functional. The top level links configured with submenus used to work in PlatformPro standard menus. I have tested this with different browser types and see the same issue. I also tested to see if I see this issue using the Nav Classic menus and I don't (the top level links work fine just like in PlatformPro). Here is a link to our site:
Is this by design for the NavBar in PageLines or is this abnormal? What is confusing is that the "select hand" mouse cursor remains active over these non-functional links indicating to users that they can click on them, but when they do, nothing happens.
I am currently on WordPress 3.4.2 (multi-user) with 14 networked sites and am getting ready to upgrade to 3.5.1. I have the following plugins currently activated and all are at their latest versions:
Akismet, version 2.5.7
All-in-One Event Calendar by Timely, version 1.10-standard
Awesome Flickr Gallery, version 3.3.6
Exec-PHP, version 4.9
Gravity Forms, version 1.7.3
Gravity Forms PayPal, version 1.7
Unfiltered MU, version 1.3.1
WP-Members, version 2.8.2
This is a hosted site on Windows Server:
Windows 2008 R2 Web
I would prefer to continue using the fixed NavBar, but would like the top level links to work if possible.
Thanks for any insite you can provide.
Posted 26 May 2013 - 04:34 PM
First, when changing themes you must also make sure your saved menu (if you have one) is assigned to the new theme using the Theme Locations panel. Just select your saved menu for the Primary menu.
The top level menu in NavBar is never linked to a location if there are child items below it. Twitter Bootstrap forces it to only open the list below it. To overcome this, just repeat the full link as a child link under the parent. Cumbersome, I know, but Twitter does it this way for a reason.
Alternatively, you can use Nav Classic in place of NavBar, which allows parent or top level links.
Posted 26 May 2013 - 05:42 PM
Thanks for your prompt reply. I had already implemented your prescribed solution to repeat the full link as a child link under the parent. I prefer not to use the Nav Classic because that menu scrolls off the screen where the fixed NavBar does not. Is there a way to prevent the mouse cursor from showing a "select" hand over the inactive top level that has child links underneath it? The way it is makes it confusing to the user because it shows that he can click on it, but nothing happens.
Posted 26 May 2013 - 05:45 PM Best Answer
Unfortunately, the cursor is part of the browser, and thus out of our control.
The primary link being among the child links is the only way to get around Twitter Bootstrap's limitations. I apologize for the inconvenience.
Posted 27 May 2013 - 06:19 PM
"Twitter does it this way for a reason." - I assume this is to follow their interface standards. Like the person who started this thread I would prefer the behaviour of the classic navbar but would like to use the new one. The workaround is not ideal. Is there no way of overriding Twitter Bootstrap limitations?
Posted 27 May 2013 - 06:50 PM
Please create a new topic with your specific questions