Beta 2 Bug - Mobile Mega Menu - Navigation

Beta
#1

Hey Team

Navigation Layered element used within a Mobile Mega Menu element has been auto-changed when installing Beta2 into a Navigation Layered Button/Toggle, rather than the actual Layered Navigation Menu - which was originally used in the Mega Menu:

Screen Shot 2021-08-02 at 12.36.15 pm
Screen Shot 2021-08-02 at 12.36.15 pm1266×731 119 KB

You can see from above that the default ‘Navigation Layered’ button is now shown, rather than the actual Layered Navigation menu itself.

Thanks
Sam

#2

Thanks Sam! Just to confirm, that element existed prior to updating? And now it shows the form with a toggle instead of just showing inline?

I ask because under the hood, it’s the same element, but with the mega menu update we forked it to simply output inline and get the modal/off canvas from it’s parent element. It looks like that might have reverted.

#3

Hey Alex

Yep, you’re spot on. Looks like it has reverted.

Was initially just showing inline, and has reverted to show the toggle.

Cheers,
Sam

#4

Likewise I have the same issue

Beta 2

Screenshot 2021-08-03 at 11.28.43
Screenshot 2021-08-03 at 11.28.431368×1036 137 KB

Live

Screenshot 2021-08-03 at 11.28.58
Screenshot 2021-08-03 at 11.28.581178×1096 129 KB

#5

Thanks for confirming Sam! And thank you Scot for the additional example. Should be able to get this one sorted out.

#6

Fixed for next patch.

1 Like
#7

Hey @alexander

This doesn’t appear to have been fixed? - using a Global Block here for the Layered Mobil Nav (live site):

Screen Shot 2021-08-24 at 12.16.30 pm
Screen Shot 2021-08-24 at 12.16.30 pm1118×1086 90.4 KB

White button should just be the Layered Navigation.

Updated to Pro 5.0.5

Thanks
Sam

#8

Hi Sam,

Thanks, I’m sorry you’re still seeing that. There might be some intermediate versions we’re not migrating from properly. You can do this to repair it:

  • Enable Dev Toolkit from Preferences and open it using the bar icon
  • Inspect the element
  • In the inspector tab of Dev Toolkit search for “legacy_region_detect”
  • Click the toggle to make sure it is “false”
  • Save the page/header/global block etc.
#9

Good to know @alexander , thanks.

I think it might be because its pulling through via a Global Block maybe? As this is what we used to have to do to implement a Nav Layered Element into a Footer.

I just re-added a ‘new’ Nav Layered Element directly into the footer and it worked fine.

But yeah, might have some users noticing this across their sites if they’ve implemented Nav Layered element for Mobile menus via Global Blocks in the past.

Cheers,
Sam

#10

Ok great! Glad to hear you got it sorted out. Yeah, it might have something to do with Global Blocks - there’s another case I saw yesterday in a Global Block as well.

#11

@alexander - FYI I have about 20+ other sites where I have used Global Blocks x Nav Layered workaround. So I’m sure there are lots of other users with this issue once they update.

Just confirming you’ll be looking into resolving this Global Blocks x Nav issue? Or will we have to manually fix all impacted sites?

Cheers,
Sam

#12

Hi Sam,

I was able to find an anomaly related to Global Blocks and get that sorted out! The fix will be in Pro 5.0.7 which will go out tomorrow or early next week.

1 Like
#13

Awesome @alexander - thanks so much for that.

Cheers,
Sam

#14

You’re welcome! We’ll be pushing the update out today, so keep an eye out for it this afternoon.