WooCommerce Conflict

Hi Roger,

Please could you send me a link to your site?
If you disable Mega Menu does it start working? (you’re safe to disable and re-enable it)

Thanks
Tom

I’ve just installed WooCommerce and those buttons are showing and working for me.

But there’s no mention of ecommerce.js on my page (just a vanilla install with WooCommerce and Mega Menu) – do you know where that script is coming from?

Yes, disabling the menu allows Woo to work properly. I also tested on different theme and Woo worked there too. It’s your menu that’s in conflict and it’s killing me because I tried two other menus before yours that weren’t very good and yours worked great…and now this.

BTW: it only conflicts with variable products, not simple. Although on simple it blocks the quantity option.

Hi Roger, could you enable the plugin and send me a link to your site?

Tomorrow evening is the next time I’ll be able to take a look.

Regards,
Tom

Hi Roger,

I’ve just released 1.1, it might fix your problems but I’m not sure as I can’t replicate it here yet, worth trying though.

I’ve tried using simple products (I’m not sure what variable ones are) but the quantity box is working on those.

If 1.1 doesn’t fix it please send me a link to your site so I can see what the problem is.

Regards,
Tom.

Hi Tom:

I got it fixed by a jquery expert. As he put it, “The script of old menu was initiated even after new script (mega menu) is there.”

So all good and we are now officially live:

https://freeportbluesandjazzfestival.com/ with Woo on a separate installation for now (this is the one that had the issue):

https://freeportbluesjazzfestival.com/

Only other issue I have is the “hover” works on FF but not on Chrome.

Hi Roger,

Good to hear you have it sorted ??

Hover is working for me in Chrome (the panel displays).

I think there might be some other JavaScript still lurking about though as there should be a 300ms delay before the panel displays, but it’s displaying instantly.

In fact… just found it at the bottom of this file:

https://freeportbluesandjazzfestival.com/wp-content/themes/woodpeckertheme/js/custom.js?ver=3.9.1

Do you know why that’s there? You shouldn’t need it.. but that depends on if other conflicts crop up when that code isn’t there (I guess that’s why it’s been added?)

Regards,
Tom.

Quick follow up, I blocked that script with adBlock, and the hover seems to be working as I would expect it to in chrome, so I think you should be safe to remove that code at the bottom of the file I linked to.

Regards,
Tom

I’m going to have my new friend the jquery expert look at this.

Re: your new update, will that affect anything we’ve already done? what specific changes did you make?

Hi Roger,

It won’t affect the JavaScript you’ve added.

It depends what you’ve done but if you were upgrading from an unmodified version of 1.0.4 (or any other version) then it’s all good. I don’t release stuff that isn’t backwards compatible, it’s not worth the hassle ??

You can see all of the changes in trac if you want to take a look: https://plugins.trac.www.ads-software.com/browser/megamenu/#trunk

There’s also a breakdown in the changelog: https://www.ads-software.com/plugins/megamenu/changelog/