Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
Dear SiteOrigin People,
As of North Version 1.2.2, the Sticky Menu is not working on my Samsung Note 4. (Using Mobile Browsers: Google Chrome, Dolphin, FireFox … All Same Results)
It was consistently working on the Note 4 prior to v1.2.2. I do still have a development site using North v1.2.0, and the Sticky Menu still works on that.
Using Size Simulators, North v1.2.2 still works in them with Sticky Menu.
Both with North Versions prior to v1.2.2 & with Size Simulators, this is the results I get …
Un-Scrolled
Scrolled
Sticky Menu is one of the best features I like about North, Please Help?
Thank you very much!
Additional Notes …
My WordPress installation for North v1.2.2 is Vanilla
Only plugins installed are: Page Builder by SiteOrigin & SiteOrigin Widgets Bundle
Hi Justin4Site
Thanks for reaching out and apologies for the hassle. You’re correct, the sticky menu has been temporarily disabled. The sticky menu on mobile was causing a flicker when scrolling the mobile menu, the issue was bad enough that if you had a long mobile menu it was extremely difficult to reach pages low down on the menu. Unfortunately, we weren’t able to quickly resolve the problem. For the moment, sticky is off on mobile, as soon as we’ve resolved the problems we’ll reactive it. It’s a priority one issue on our list and should hopefully be fixed in an update in the next week or so.
The original issue report is here: https://github.com/siteorigin/siteorigin-north/issues/126. We’ve been hard at work improving the theme, if you’re interested, you can check out the last month’s pulse here: https://github.com/siteorigin/siteorigin-north/pulse/monthly. Hope to have this problem solved soon. Sticky is still working on desktop.
Ahhh OK … Thank you Andrew & Thanks for the Links too!
For sure. Thanks for your understanding. We’ll get this sorted ASAP.
I was wondering if this problem been resolved? It seems to still not be working?
Thanks,
Kim