Latest version seems to break woo functionality

Hey @chucklebum0205

Thanks so much for reaching out to us about Facebook for WooCommerce! I’m happy to help out. ??

Sorry to hear that the latest version is causing issues with Yoast and other plugins, that is certainly not expected behavior from our plugin. Could I ask you to please open up a support request with us here?

https://www.skyverge.com/contact/

Please do reference this forum thread and also include your system status.

You can get the report by going to:

WooCommerce > Status and clicking on Get system report.

Cheers,
Steve

Yes, confirming the bug also.
When do you expect to release a hotfix?
Thanks.

Hey @darrenmcentee and @chucklebum0205!

Thanks for letting us know about this issue. It would be great to get a bit more information about the problem so that we can pass this on to our developers. Right now, I don’t have an expected release date for a hotfix, as we’re not able to replicate the same issue you’re seeing.

We’ve installed the free Yoast SEO plugin, yet everything behaves as expected. If you can share some more information on exactly what plugin needs to be active in order for the error to occur, or the steps you took before the error occurred, or provide us a system status report to look over the list of Yoast plugins that you mentioned, this would help us greatly speed up a resolution to the problem.

As Steve mentioned, perhaps the quickest way to get to the bottom of the issue would be to provide us access to a staging environment so that we can find the exact plugin that is causing this.

To do that, please could you raise a support request via our support form? Altenratively, I look forward to hearing from you with further details!

Cheers,

Simon.

Hi Guys,

I’ve found a plugin that doesn’t seem to like the new update of facebook to woocommerce on my setup at least and it’s this one:

https://www.ads-software.com/plugins/disable-admin-notices/

Disabling this plugin and everything works fine with the latest version of your plugin. If I want to use the disable admin notices plugin then I have to use your previous version (1.10.2) of the plugin.

Hope this helps diagnose what’s going on. Looks like a conflict for loading js scripts within the admin.

Kind regards

Brian.

• This reply was modified 4 years, 10 months ago by chucklebum0205.

Hey @chucklebum0205!

Thanks so much for taking the time to investigate that for us. I’ve just given this plugin an install on my site using v1.11.0 of Facebook for WooCommerce and WooCommerce v4, and I don’t see an error just yet.

Is there any particular action or page where this error occurs for you?

Cheers!

Simon.

I am getting the error on this when using the WooCommerce “Quick Edit” function on products.

Chrome console:

Uncaught DOMException: Failed to execute 'insertBefore' on 'Node': The new child element contains the parent.
    at HTMLDivElement.<anonymous> (www.....com/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,utils&ver=5.4:3:23139)

This has happened on multiple sites running v1.11.0
Thanks,
Darren.

• This reply was modified 4 years, 10 months ago by dmac.

Hi simon,

Like Darren mentions it seems to occur when editing products – eg you can’t edit a product image as it doesn’t open in an I frame – a lot of the functionality of the edit product page eg yoast seo you can’t see etc as it looks as though some required JavaScript doesn’t get loaded in due to the error I first mentioned in my original post. This doesn’t happen when using v1.10.2 is used or when the other plugin that I’ve mentioned is disabled – it could be other plugins will affect your plugins behaviour too in a similar way.

• This reply was modified 4 years, 10 months ago by chucklebum0205.

Hey @chucklebum0205 / @darrenmcentee,

Thanks so much for all the information here. I’m still struggling to replicate the issue on my local test site with these plugins and directions. I have Yoast SEO active, along with Disable Admin Notices, and yet I’m still able to edit the product images, use the Quick Edit function, and view the Yoast SEO fields on the edit product screen. At all times I’ve kept the console window open with preserve log enabled, and no error like the one you both are seeing is being logged.

There appears to be some key ingredient that I’m missing in order to replicate this, so I’d love a closer look. If either of you are able to contact us, I’d love a chance to look at your sites directly with a temporary login. It would also be preferable to view a staging site so that I could run conflict testing as you already have done to try and see where this might be coming from.

Would either of you be able to share a temporary login by using our support form link above, and let me know when you’ve sent the request?

Cheers!

Simon.

Hi, does this fix this issue?
2020.05.04 – VERSION 1.11.2
Misc – Add support for WooCommerce 4.1

Thanks.

Hey @darrenmcentee!

Thanks for checking up here. Our developers are still investigating the root cause of this issue. In the meantime, we did manage to see that the error only occurs when the admin notice is output to screen on certain pages.

Due to this, it is possible to use a custom snippet to dismiss the notice on next login, so that it no longer outputs the admin notice and avoids the error altogether! This seemed to work in a few cases it was tested on, and one merchant reported success.

If you’d like to give this a go, you can find the snippet here: https://gist.github.com/da4454d97e3012a03f6d64ad9ec9949b

Please note that the snippet will run on each page load, so I would advise to only keep the snippet active for the initial login of your admins. The issue should not show itself once the notice has been dismissed, and therefore the snippet isn’t required to be active after that.

You can add this snippet to your theme’s function.php file, or use a plugin such as Code Snippets which is a favorite of mine, as this allows easy activation/deactivation and safe mode should anything go wrong!

Will you be giving this snippet a go or waiting for a future fix in the plugin?

Cheers!

Simon.

Hi Guys,

Just to let you know that i upgraded to the latest version of the plugin and my issue seems to have gone away!

This is without adding the snippet you’ve mentioned.

Cheers

Brian.

Confirming this is resolved in 1.11.2.
Thank you.

Hey @darrenmcentee @chucklebum0205!

Well, that’s great news! I’m not quite sure if the developers intended to fix this specific issue, though it’s quite possible they did and I didn’t notice ??

Thanks so much for confirming, I’m very glad we were able to get this one patched up for you.

I’ll go ahead and mark this as resolved now then, but if you have any other queries or issues, please don’t hesitate to let me know.

Cheers,

Simon.

Sorry, still getting the issues again.
Issues seems to be back. Rolling back to v 1.10.2 and the problem goes away.

Hey @darrenmcentee,

Were you able to give the workaround I suggested in my previous reply a try? This should hide the notice that was causing the error in our tests to be shown. So while not a true fix, it should avoid the issue for you in the meantime.

Could you let me know if this isn’t working if you’re able to give it a try?

Cheers!

Simon.