Submenus on Mobile menu do not display after Update to 3.1.0. from 3.0.7

Hello @cezarina,

Sorry for the inconvenience, and thank you for your report,
This is forwarded to the developer team, and it will be fixed/improved for the next update(s).

For a temporary solution, please use the CSS below. Please put the CSS below in Customizing > Custom CSS/JS > CSS Code:

#mobile-fullscreen ul ul.sub-menu {
    display: none;
}

.open-sub ul.sub-menu {
    display: block !important;
    visibility: visible !important;
    opacity: 1 !important;
}

Note: if you have a cache plugin or server cache. You need to clear its cache contents or disable them to see your changes.

Best Regards

Hello,

I can confirm the issue described by Cezarina with the vertical header also. After update to 3.1.0. from 3.0.7, some white space is added between menus and submenus and the submenus aren’t visible.

I’ve rolled over to 3.0.7 and I’ve resolved this but please do more testing before releasing new builds…

Luckily I’ve tested this on a staging version, but I’ve lost a few hours trying to find out what is the issue because I’ve made a bunch of other updates and didn’t know that the culprit is with OceanWP.

P.S 1: The above snippet didn’t worked for me for the issue on vertical header, I’ve tried it before rolling back.

P.S.2: I’m also a paid user of OceanWp addons and this isn’t the first time this kind of issues are released without thorough testing from developers. Please consider this as a feedback for future releases.

Thanks @skalanter for your prompt reply.
I would prefer waiting until the next update with your solution to this problem instead of adding additional CSS code. If the next update won’t fix this, I’ll carry on with the code.
Is that all right or you advise otherwise?

Thanks again for your valuable help!
Cezarina

Hello @daniel-mesteru,

You’re right, this isn’t the first time we rolled out an update with issues or smaller bugs. I wish I could tell you that would never happen again, but that’s just impossible and no one can guarantee that.

The fact remains that no matter how much effort we put into testing, we will absolutely never ever be in the position to replicate all thousands and thousands of scenarios, settings, environments, etc. Things like these happen even to companies like Microsoft, Tesla or Facebook who have more QA employees than we can possibly imagine.

On the other hand, if you do wish to get involved in beta testing and help us release more stable and smoother versions by thorough testing of pre-release versions we’d send, you can reach us and we’ll discuss the possible options: https://oceanwp.org/pre-purchase-question/

Thank you for your understanding and continued support

Hello @cezarina,

Thank you for your feedback.

We’ll definitely fix this with the next release, so the decision rests with you.

You can either update and apply the temporary code, then remove it after the next update, or you can simply wait for the next release.

In the meantime, in case you update any other test / staging sites and notice any other problems, kindly let us know.

Thank you very much for your fast report on this matter and for your help.

Have a great day

Thanks @wpfleek,

I’ll wait untul the next release then and take it from there.
I’ll also let you know in case of other issues. Thanks again for your efforts.

Great day to you, too!

Cezarina

I have the Child Theme Pluggin. Can I update it and how and keep it. What should I do. I don;t think I have any issues with it. Thanks.

Bridget Schaas [email protected]
https://tarotpathoflight.com my website