deejayone
Forum Replies Created
-
Thanks for the reply.
Can confirm Facebook for WooCommerce is version 2.1.4
In case it matters, WooCommerce is 4.6.2 and WordPress is 5.5.3 (I keep everything as up to date as possible).
Problem still persists.
Hi,
Anybody able to help at all?
Still getting issues. 🙁
OK, thanks. So I’m at a loss as to what would have deleted the feed. I assumed it got deleted when the feed was deactivated.
In any case, do you have any idea as to why the feeds will not reactivate again after being deactivated?
As per my previous post:
If I duplicate the feed, it runs OK first time and creates the XML feed.
If I create a new feed it runs OK first time and creates the XML feed.
The initial feed looks like it is refreshing, but always resolves to a 404 error instead of the XML feed.
So it can create/duplicate a feed OK, which is great! But my worry is whether it will refresh the feed properly or whether it will reactivate and run if I deactivate it for any reason.
If I duplicate the feed, it runs OK first time and creates the XML feed.
If I create a new feed it runs OK first time and creates the XML feed.
The initial feed will looks like it is refreshing, but always resolves to a 404 error instead of the XML feed.
So it can create/duplicate a feed OK, which is great! But my worry is whether it will refresh the feed properly or whether it will reactivate and run if I deactivate it for any reason.
The feed will have deleted when I deactivated it to test the deactivation/reactivation issue.
I’ve since reactivated using the force-active URL because it remains stuck inactive otherwise.
Unfortunately it will not now create a replacement feed when refreshing the feed, or when it’s scheduled refresh takes place (although it always looks like it is going to as it goes through all the processing %ages until it is ‘ready’ again).
Thanks again for the reply.
I have reduced batch size down to 100.
I have also added 3 extra CPUs to my cloud hosting plan (which is set to auto-scale under load in any case).
My server load stats don’t show any significant CPU spikes when refreshing the feed.
My hosts have increased server execution time to the maximum allowed, apparently.
Also, there are no fatal error logs recorded in Woocommerce since the 29th (posted earlier in the thread). So nothing showing it is exceeding CPU usage.
Unfortunately non of these have solved the issue. The feed appears to be refreshing and passes 100% to Ready, but the URL is still resolving to a 404 error.
Plus… I’m still getting the problem that the feed won’t reactivate if I deactivate it (unless I use the force-active string in the URL).
🙁
OK, so the problem of being unable to reactivate remains.
Also now the feed has re-run and is returning a 404 page for the feed link.
So… reducing the batch size to 200 worked for the first run, then when it run again on a scheduled basis it returned an empty feed/404 page. Upon manually refreshing the feed, it processes but still returns a 404 page.
Any further ideas?
Ahhh, interestingly reducing to 200 didn’t work at first, but seems to have worked after deactivating/reactivating the plugin.
However… I have tested deactivating and reactivating the feed and whilst it will deactivate, it won’t reactivate again without using the force-active=true string in the URL.
I have a total of one fatal error log, which is dated yesterday. This is the entirety of the log:
2020-09-29T18:53:35+00:00 CRITICAL Maximum execution time of 120 seconds exceeded in /home/************/public_html/wp-content/object-cache.php on line 153
2020-09-29T19:01:45+00:00 CRITICAL Allowed memory size of 1048576000 bytes exhausted (tried to allocate 134217736 bytes) in /home/************/public_html/wp-content/object-cache.php on line 255
I think these errors must’ve kicked in when I was trying to debug this problem yesterday. but the issue absolutely started days before this.
Sure.
Thank you. I have gone through all those and can confirm everything is seemingly as it should be (note: I made no changes to the feed or settings at all in weeks; it was working fine until a couple of days ago and now isn’t). The only reason the feed is empty is that I deactivated the feed (which apparently wiped the feed) and tried to reactivate it, but — as stated — it won’t reactivate properly.
There is one fatal error log dated several days ago, with no applicable errors by the looks of it.
I have tried lowering the batch size to 500, but that doesn’t resolve the issue.
As stated, the problem isn’t necessarily just with the feed not updating, for some reason when I deactivate it it won’t reactivate unless I use force it using the query string so not sure if that is indicative of something else?
I’ve also tried changing the refresh intervals (it doesn’t seem to run) and have tried several times to refresh manually but other than the initial ‘processing 0%’ flashing it just stops and doesn’t run the refresh.
Honestly, I’m at a loss with this.