I’m having the same problem. I cannot edit my WooCommerce products.
Checking the “Programmed Actions” in the WooCommerce “Status” page, I realized that I have a lot of failed actions, and they are all from “wc_facebook_regenerate_feed”. They all say that “the action timed out after 300 seconds”. They all started a couple of days ago, I’m assuming maybe after the last update.
I tried deleting the product catalog from Facebook, and re-connecting the plugin, but this also didn’t work, and now my Facebook and Instagram stores are not showing because they don’t have products.
Bottom line, something is wrong with the catalog syncing, and it times out. This didn’t happened before with my settings, so it’s not a “not enough memory” problem.
Same problem here, I can’t edit my WooCommerce products…
Hey @zahost!
Thanks for writing in here, I appreciate it! We’re aware of a potential issue here. Can I ask you to confirm if the products this is happening with are variable products?
Thanks for any other details!
@gmedel – as I mentioned in the prior thread, would you please open your own topic, so that we can comply with the forum guidelines? Thanks!
@napslife – In order to comply with forum guidelines, would you please open your own thread with a paste of your system status so I can get a better idea of what might be going on? You can grab it by going to:
WooCommerce > Status and clicking on Get system report.
Additionally, is this happening with all product types or just variable products? Please do answer me in your new thread.
Thanks, everyone!
Julie 🙂
SkyVerge
Thread Starter
zahost
(@zahost)
Hi @julieskyverge
In my case it is only simple products, as I don’t have any variable products listed at the moment.
Hi @zahost,
That’s interesting, thank you for letting me know. We’d previously seen an issue with variable products and that should have been resolved, though I don’t think it had cropped up with simple products.
Would you please be able to paste your system status here so I can get a better idea of what might be going on? You can grab it by going to:
WooCommerce > Status and clicking on Get system report.
Thank you!
Julie 🙂
SkyVerge
Thread Starter
zahost
(@zahost)
@julieskyverge Which part/parts of the system report are you interested in? I’m not comfortable publishing the entire report on a public space.
-
This reply was modified 5 years, 6 months ago by
zahost.
Hey @zahost!
Thanks for getting back to us, that’s understandable! I’ve had a look over your description and it sounds as though there might be some front-end issues causing these errors, as it’s certainly not something we’re seeing widespread at the moment.
It would be great if you could confirm if with only WooCommerce and Facebook for WooCommerce active, do you see the same error? You mentioned that you attempted to deactivate other plugins and it disappeared when Facebook for WooCommerce was deactivated. I wonder there is a conflict between another plugin, and so if either of the plugins are deactivated, the problem would disappear. If this was the case, being able to narrow this down would let us offer some suggestions to get this working again!
Another option would be to check the browser console when you’re on the edit product page with the broken Screen Options. Here’s a list of common ways to access the console for different browsers: https://documentation.concrete5.org/tutorials/how-open-browser-console-view-errors
Would you be able to let me know if you see any errors logged after trying to access Screen Options?
Cheers!
Simon.
Thread Starter
zahost
(@zahost)
Hi @simonskyverge
With all plugins activated, I get a “500 internal server error” in the console.
It does not generate any additional errors by clicking on screen options. It just does nothing.
No errors are showing when clicking on the edit product image. The popup does not load. Instead, a new page loads without errors, showing me only the ancient library interface.
Clicking on the “Add product gallery images” link generates the following error
Uncaught TypeError: wp.media.controller.Library is not a constructor (meta-boxes-product.min.js:1:11107)
Nothing happens on the page itself though.
When I deactivate the Facebook plugin, no errors show any longer and everything works as expected.
Running only Woocommerce and Facebook for Woocommerce is not an option though. The act of deactivating plugins already caused unnecessary reworks on parts of my site. Still, I deactivated the non-essential plugins I’m willing to sacrifice, but the problem still persists with FB 4 WC. From what I can see, it only affects the product image selection and gallery as I described above, and it prevents the screen options drop-down from working. The latter is confined to the product edit page. It doesn’t affect the drop-down in the product list page. It doesn’t break anything else as far as I can tell, and it does what it is supposed to do. It just seems that it is blocking the product edit page from loading correctly.
Hi @zahost,
Thanks for running those tests!
The console error is interesting as it suggests that WooCommerce hasn’t been able to load the scripts completely, which also suggests another conflict. The Internal Server Error should have produced some logging either with the WordPress debug logging, or within the PHP logs on your server too. If we could find out what that error is, that would definitely help us to track this down for you!
I can certainly appreciate it’s not always possible to fully conflict test on a live site. Would it be possible for us to get access to a staging site where we could look at this more closely?
Cheers!
Simon.
Thread Starter
zahost
(@zahost)
@simonskyverge I think that it quite obvious that Woocommerce is not loading the scripts completely, which suggest a conflict with your plugin, as none of the other plugins causes the behavior in question. Unfortunately, my staging environment is occupied with other work, and setting up another and cloning my site for the little benefit I’ll get out of it, is not worth the effort. Deactivating the plugin for editing purposes is the dirty workaround I’ll use. It takes up much less of my time than to try and get this resolved. If I get some more spare time, I’ll go and dig through the debug logs to see what I can find. I can’t commit to any time-frame though. I’m unsure if this topic should be marked as “resolved” in the absence of other options in the meantime, or just leave it open. Let me know how you wish to manage further exploration of this issue.
Hey @zahost,
Julie here, chiming in for Simon. We can resolve this for now and you can open up a new thread if you have time to go through some of the debug logs.
I should note that Automattic is taking over the development and support of the Facebook plugin, so they’ll be handling support in this forum as well going forward.
Having said that, I’m sorry we couldn’t resolve this more thoroughly apart from the workaround that seems to do the trick. Please don’t hesitate to open up a new thread if you have the time and inclination to dig deeper in the future and our friends at Automattic will be happy to help.
Thank you so much for your efforts!
Julie 🙂
SkyVerge
