I have to say this has been a bizarre experience.
– my host doesn’t allow cron jobs (it’s running on Plesk)
– EasyCron stopped working after the trial period.
– cron-job worked but threw a 302 error message.
– after a week working, I rechecked and discovered cron-job had cancelled the job due to the 302 error messages even though set not to. It turned out EasyCron had turned back on and was driving it. But I’d closed that account first, before realizing it was the one actually working.
– I cancelled both and turned WP-cron back on and it worked fine for over a week! Until the ROP plugin announced it may not be working. Are you sure it’s not the plugin check that is causing it to stop working?
Hi there, the plugin check works off admin_notices() we check whether the plugin is activated and if it’s scheduled task exists, if it scheduled task exists, and has not been fired after 1 hour, which would clearly be an issue, then we have the plugin show a notice
The code for this can be seen here: https://gist.github.com/UVLabs/f26c0f987778592451440982cb63d523
So ROP is simply informing you that something is wrong with it’s scheduled task, you can use WP Control to verify that indeed ROP and other scheduled tasks might not be running.
I believe that the issue is due to your website environment, you can contact your web host for what alternatives they have for creating True cron jobs the alternatives such as easycron and cron-job.org do work as you have seen, I have also tested these myself as well as many other users.
Error 302 is a redirection notice, which tells you that the request was redirected at least once before it got to it’s destination. So indeed the issue here is due to your environment and not the actual plugin.
If your host does not support other means of creating a true cron job then I’d recommend using one of the alternatives we’ve covered and possibly investigating why there’s an Error 302 being sent back, maybe try turning off the authentication you have happening and look into other methods of protecting wp-admin by implementing a recapture + strong login password
Thanks, Uriahs. Sorry to be grumpy but this has been an odd problem. I value ROP as it effectively resurfaces a large catalogue of articles. But none of the solutions has been reliable or possible.
I’ll loop back and talk to my host.
