- This topic has 4 replies, 2 voices, and was last updated 3 years, 6 months ago by
.
-
Posts
-
Hi there,
I have been working on a staging site and propagated my work to another that is linked to my live site to push to live.
It all has been successful except for one bit, where the secondary navigation menu is appearing above the header elements, rather than below on mobile:
Where I want it to appear below the last header element, as shown here:
I have no idea why this is the case and what would be the way for it to look normal?
To view staging site in question:
Link to page
Username to view: fmgvtsbagd
Password to view: 5yQX7eS5tPI have code that you have recommended me to add over a few support tickets such as:
The element:
Two snippets:
I tried to disable both snippets to no success – how do I get the secondary navigation menu below the two header elements?
Many thanks,
I’ve found a fix which is good – although strange – deleting the element code for the secondary menu above and repasting it back in again.
I find this happens a bit with GP – when you publish elements in a different order, the locations of those elements changes – is there a reason for this?
Customer Support
Hi there,
that sounds like the returned content of that function may have got cached. If it happens again try clearing any server/plugin page caches.
I’ve just done a test and it without any caches whatsoever, it appears the order in which elements are published for the name hook will change the positioning of them, even if priorities and code is added to change them – is this normal? Just trying to understand it!
With GP Elements, if you have a bunch of Elements that all use the same hook, and the Priorities are all the same, then the order they are executed/displayed in will be the published order. This should never be any different, and the only reason you may see differently is if caching is in play.
- You must be logged in to reply to this topic.
