-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feeds are not automatically updated via the Wordpress CRON job #883
Comments
After the Version 4.4.3 (2024-02-09) update it seems to work as expected. I have to monitor for several days to make sure, but if all works I will update this post and close the issue. |
I am still experiencing issues with the plugin. I have two sites, one which pulls from six wordpress sites, the other pulls from eleven sites, mostly wordpress. I installed the WP-Cron Status Checker plugin, and every 24 hours it emails a report. I can see there are errors every hour when the Feedzy job runs. The job fails randomly from 2100ms to 12,000ms after it starts running. Here's that log:
I've installed a cron logger plugin, so hopefully I can view these errors. Maybe the PHP config on my server isn't quite tuned for this type of plugin? |
Update: This is still unreliable for me. After monitoring it for the past 2 or so days the first 2-3 feeds that have around 60 feeds each, are updated, but not rest. I do not know what I can do to debug this. I think Feedzy should output some errors in case some PHP/Nginx configs are not well setup for how many feeds it needs to pull from. EDIT: I forgot to mention that rarely it can update all of the feeds. But that's rare. |
Hi @tio-trom, Thank you for sharing your experience on this issue with the cron jobs. We will try to replicate this problem on our end and will update this issue. |
I want to share all of my feeds and groups so you can test on your own system, since this is not reliable. Rarely it updates all of them, but most of the time it simply updates the few groups. So here they are in order: News – Society
News – Tech and Internet
News – Science
News – Environment
News – Health
Videos – 2
Videos – 1
Photography
Interesting Stuff
Maybe you can please test this on your end. I am unsure what I can do to test more. Thanks! |
Hey @tio-trom, I found nothing suspicious with running all the feeds from the CRON job. One thing that I suspect is that maybe a bug appears in some specific import settings and stops the update loop starter by the CRON. If possible, you can test this proposed solution 🔧 #897 (comment) and see if it works. for you. Also, it will be very helpful if you have the possibility to post screenshots with the settings that you use on those feeds 🙏 |
Thank you for your input. For the past ours I tested that version of Feedzy and I see no change unfortunately...I also suspect that the cron job comes across some errors with some feeds and cannot move on past that so it gets stuck. I noticed that at times the first 2-3 groups of feeds get updated via CRON, and only them. So I disable the 4th group to see if that's the one that holds the rest from updating and yes at times that fixes it, as if it can skip the 4th and moves on. These are all of the changes I made for them all. |
Thanks for the @tio-trom feedback. By 4th group, you mean the If not, can you point to the wrong group of links 🙏 ? I will check them individually 🔍 |
Unfortunately this happens with different groups...for the past hours it happened to another group. Since I cannot see any errors we cannot know if there are some particular feeds that are stopping the update. But this happens randomly to different groups. Isn't there a way to enable a debug mode for Feedzy so we can see what happens behind the scene? |
@tio-trom, you can enable the debug log by changing the the feedzy-rss-feeds/feedzy-rss-feed.php Line 131 in 60f3680
It should be changed to Note Make sure to have the debug mode enabled on your website: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/ |
Ok here is the debug https://paste.trom.tf/haqucufeda.yaml - I was looking at it but I am not qualified to make much sense of it :). The only suspicious thing I found is this:
|
I've also noticed that for now the problematic groups are these: News - Science:
News - Tech and Internet:
|
Thanks, this was the problem. The plugin was trying to use a feature of the Pro version and in its absence, it was crashing the cron for feeds that were missing the featured image URL. The fix will be a part of the next release 🚀 |
Oh that'd be amazing if this will be fixed! Thank you so much! |
I have manually applied the fix from #897 and now it all works correctly. So you know. Again, thank you. Am very happy that it was fixed! |
Description
I have reported it here https://wordpress.org/support/topic/feeds-do-not-get-updated/ but I think this needs to be escalated further because it is a major bug, if it is a bug and not a server limitation which I doubt.
I have 6 feeds:
News (with some 60 sources),
Videos (with some 100 sources),
Photography (around 15 sources),
Interesting (some 30 sources),
Illustrations (1 source),
and VideoNeat (1 source).
In that exact order.
Each is setup to only pull 5 posts. The cron job for feedzy is every 30 minutes.
My server should be capable enough for this job.
However only the News feed is triggered via the CRON, and even then at times it can pull some new posts, at times pulls none despite there being available posts since I can try with the manual RUN NOW button. Rarely the other feeds get updated, but very rarely.
Thus it is not reliable at all.
Mind you it all works super fast if I manually click RUN NOW, even if I do so for all of them one after the other, quickly. Whys is the CRON job failing to update the feeds?
Step-by-step reproduction instructions
Screenshots, screen recording, code snippet or Help Scout ticket
I am using Feedzy v4.4.1 and I can provide access to the website if any Feedzy developer wants to investigate more.
Environment info
No response
Is the issue you are reporting a regression
No
The text was updated successfully, but these errors were encountered: