What the plugin does, is create a duplicate clone of the sticky element, and once it needs to be sticky, the original (moving one) is made invisible while the sticky one is made visible.
In your case, the original doesn’t become invisible, because it contains a mega menu that is specifically set to be visible at all times, even when the parent is set to invisible (line 111 from styles.css):
#mega-menu-wrap-max_mega_menu_1 #mega-menu-max_mega_menu_1 {
visibility: visible;
text-align: left;
padding: 0px 0px 0px 0px;
}
I believe you can fix the issue by removing the line:
visibility: visible;
If that’s not an option, or if it doesn’t work, try adding this to your CSS:
#mega-menu-wrap-max_mega_menu_1 #mega-menu-max_mega_menu_1 {
visibility: inherit;
}
Thread Starter
BitEdge
(@whatwhatwhatwhat)
Thanks Mark,
I cant find
#mega-menu-wrap-max_mega_menu_1 #mega-menu-max_mega_menu_1 {
visibility: visible;
text-align: left;
padding: 0px 0px 0px 0px;
}
In any css file, where is that exactly?
I added
#mega-menu-wrap-max_mega_menu_1 #mega-menu-max_mega_menu_1 {
visibility: inherit;
}
to my theme’s css and it seems to have help a bit, it might have even fixed the problem happening with that top menu widget but now the same problem is happening with the HTML widget below it. Can we think of a way to fix that one?
Cheers
This happens because there is a transition applied to all your links:
a {
transition: all 0.2s ease-in-out;
-moz-transition: all 0.2s ease-in-out;
-webkit-transition: all 0.2s ease-in-out;
-o-transition: all 0.2s ease-in-out;
}
Because of that, when the element becomes invisible (to be replaced by the sticky cloned version) it won’t go invisible right away, but the links in your element will go from visible to invisible with a 0.2s transition.
You could remove the transition from links for this block by adding this:
aside.sidebar a {
transition: all 0.2s ease-in-out;
-moz-transition: all 0.2s ease-in-out;
-webkit-transition: all 0.2s ease-in-out;
-o-transition: all 0.2s ease-in-out;
}
Another option is to give the entire block a white background, so that the transition will just not be visible:
aside.sidebar {
background-color:#ffffff;
}
BTW, the Megamenu code can be found in http://www.staging1.bitedge.co/wp-content/uploads/maxmegamenu/style.css?ver=c134b1
I’m not sure how that plugin works and how that CSS file ends up in that location, so I’m not sure if it’s safe to edit that file. I wouldn’t, cause adding the CSS yourself seemed to work already.
Thread Starter
BitEdge
(@whatwhatwhatwhat)
Thanks, I did
aside.sidebar {
background-color:#f9f9f9;
}
And it helped, now we are on production
http://www.bitedge.co/
there are 2 last bugs, see what happens When an accordion of that top menu is open (by clicking Basketball odds for example) and the user scrolls down.
1.
The accordion closes
2.
The accordion section remains displayed, visible above the “Bitcoin odds comparison” title as the user scrolls down.
Thanks for your help, I have given the plugin a 5 star review 🙂
Thank you for your review, much appreciated! 🙂
For bug #1, try turning on Dynamic Mode in the plugin settings. I’m not actually sure if that will fix it, but if the Megamenu works the way I think it works, Dynamic Mode may be the solution here.
For bug #2, I’m not really sure what you mean? I don’t see anything above “Bitcoin odds comparisons”, whether my Basketball menu is open or not, and when I’m scrolling up or down. Please elaborate?
Thread Starter
BitEdge
(@whatwhatwhatwhat)
Thanks we are very close. We have one bug with dynamic mode on and a different bug with dynamic mode off, what fun!
Dynamic mode on
If the user scrolls down the accordion menus don’t work, clicking a closed accordion does not open it and clicking an open accordion does not close it.
Dynamic mode off
If a user expands an accordion then scrolls down the accordion is no longer expanded. Similarly if a user scrolls down, then expands an accordion then scrolls up it will no longer be expanded.
I’m afraid that this goes into territory where the Megamenu isn’t fully compatible with my plugin (and vice versa).
Since we’re essentially talking about two menus (one that’s used normally, and one that’s used when it’s sticky), the state that one is in does not always update the state of the other one in real time. The only time where this happens (in dynamic mode at least) is the moment from non-sticky to sticky.
It can be fixed, but unfortunately not within the current options of the plugin, and it would take a some customized Javascript code.