I know your working on layers and stuff…so this might be invalid but as you know when putting galleries on a page inside a container or grid etc the menus come to the foreground so I was just putting a gallery straight on a page and they worked ok…ie the menus didnt overlap the images…since latest beta this doesn’t work anymore 
@Godber Yes, this will all be fixed with the upcoming V2 components!
While I have your attention… I know the existing Navbar wasn’t working for you. Are there any features or fixes you need for it?
We’re working on a new standard V2 Navbar, so it’d be good to know to make sure we get it right…
not so much it wasnt working for me…was things like I couldn’t hide pages from the menu which I know you have switched off for now.
I think I mentioned this before regarding the new Navbar? If you have a site that is secured by (for example) Sitelok by Vibralogix, your navbar menu will likely have a restricted set of tabs that increase once you log in. It would be useful to be able to have access to the menu items such that php code could be injected (per navbar menu item) to determine whether a navbar menu item should be output or not i.e. whether you are logged in or not. It would be the logical equivalent of having a @if(loggedIn) statement for a logged in navbar menu item, if it were written using the Elements API, although in this case it is PHP which is needed.
Having a facility such as this would take menubar navigation to the next level. Currently using Stacks and Foundry, this can’t be done which means you have to have two separate nav bars; one to display when logged in and one to display when logged out. Whilst this works, it does create an issue if you do any updates to the common part as you have to do two updates and try and keep them in step.
That really sounds like a perfect use case for a custom component 
1 Like
Possibly but it would want to be be totally based on the new V2 Nav Bar with the only change being the ability to decide whether a Navbar Menu item is displayed or not.
As you are developing the new Navbar, it just seems a better idea to be able to accomodate hooks in it?
Given the amount of effort you guys have put into or are putting into creating a Navbar, doing a one-off Custom Component to replicate it seems like a bad idea?
whoosh that was the sound of these comments going straight over my head
1 Like