Re: Gantry 4 - Menu issue when using Text placeholders as parent
Posted 12 years 5 months ago
Any news on this? It seems quite a critical problem despite my calling it a 'small problem' above - Today I updated to the new Gantry and made sure my RokNavMenu is also the latest (v2.0).. cleared cache too - but the problem remains...
It means mobile users are being denied, in some cases, huge chunks of the intended navigation menu.....
Re: Gantry 4 - Menu issue when using Text placeholders as parent
Posted 12 years 5 months ago
hi there,
if you check the latest gantry 4.1 rocketlauncher install, there is also a text separator menu item 'features' and it shows fine in the mobile panel menu along with all the children.
if that's not what you meant, could you post a link to your site?
Re: Gantry 4 - Menu issue when using Text placeholders as parent
Posted 12 years 5 months ago
Thanks Kat,
To see what I mean take a look at
www.soci.ky
- On maximised screen view, menu is as expected... Shrink the page size down so the menu changes to a dropdown, and you'll see that, for example, the "Our Sports" menu disappears completely......
This seems to happen because the "Our Sports" parent is a text separator menu item...
I have Gantry 4.1 and RokNavMenu 2.0.... Is there something I need to activate to get this working as you'd expect? Sorry if I didn't quite follow your pointer above....
Re: Gantry 4 - Menu issue when using Text placeholders as parent
Posted 12 years 5 months ago
Well the new menu system of 4.1 is in the menu of the template. It seems you have already customized the 4.0 template so you will not see it in your template unless you upgrade the template to the 4.1 version also. NOTE: you will have to make any template modifications again.
Re: Gantry 4 - Menu issue when using Text placeholders as parent
Posted 12 years 5 months ago
Ah yes - Perfect! All working good after I updated template - Apologies I thought the auto-notification to update Gantry in the back-end would take care of the underlying template too... so I wasn't checking that version number...