WP-Cron issue with PublishPress Revisions

Hi @mtarr

Can you try check your wp-config.php file and see if you find something like this:
define(‘DISABLE_WP_CRON’, true);

If yes, change the value from true to false.

Thanks,

Thanks for the idea, Riza. I’ll pass it to the host technical support guy — with the new hosting arrangement I can’t get access to the file!

Reply from my host:

“Per our previous discussion, this *is* in place, but it’s enabled deeper on the server. This is set here to prevent users from making changes to this as we rely on wp_cron internally to make sure certain things are working, such as cache clearing and WordPress auto-updating.

“So in essence, whilst that does exist in wp-config.php, wp_cron is enabled anyway and as such they shouldn’t outright stop their plugin from working just because it has that in the wp-config.php.”

IOW, it seems as if I’ll have to change hosting platform or stop using the plug-in. Not a happy bunny!

If you take a look at Revisions > Settings > Scheduled Revisions, there is a setting labeled “Use WP-Cron scheduling.”

You can try disabling that, nothing the disclaimer that the alternate scheduling mechanism will not work on all sites. We had a lot of conflicts with object caching plugins; that’s why we went to WP-Cron.

@mtarr Since your host is actually using the WP-Cron queue with its own triggering mechanism, you can re-enable that solution by adding the following code snippet to your theme’s functions.php (or an equivalent code module you maintain):

add_filter('revisionary_wp_cron_disabled', function($cron_disabled) { return false; });

Can you ask your host if they provide some flag by which a plugin could detect this WP-Cron implementation?

Thanks for the idea, Riza, but I’d already tried that.

Problem with your idea, Kevin, is that I don’t have access to edit functions.php.

To resolve a PHP version problems, 34sp.com had moved me to their dedicated WordPress hosting package, which is designed for security, and has proved a pain. Not only does PublishPress not work as intended, but earlier today I found a problem with My Calendar … I had two sites with a common calendar, with one calling up the other’s database. I was told this was explicitly disallowed, though there might be a complicated workround.

At that stage I pulled the plug, and asked them to go back to their original hosting package. They’ve done that, the DNS has re-pointed successfully, and all the plug-ins now work.

I’m closing this thread, but I’ll leave my problem page around in case it helps others.

Thanks for all your input.

• This reply was modified 2 years, 6 months ago by mtarr.

@mtarr Please update to Revisions 3.1.6, which we released this afternoon. It includes an accommodation for your WP-Cron usage. Go to Revisions > Settings > Scheduled Revisions and ensure “Site uses a custom trigger for WP-Cron tasks” is checked.

Thanks, Kevin … as I said in my email reply an hour before you wrote “At that stage I pulled the plug, and asked them to go back to their original hosting package. They’ve done that, the DNS has re-pointed successfully, and all the plug-ins now work.”

I’ve sent your information to 34sp, so that they know for next time someone has a problem that PublishPress can be made to work, but the solution came too late for me. My decision to revert was confirmed by the fact that I had discovered a problem with another plug-in that was caused by the greater security settings on the dedicated WP hosting.

Well done for sorting the problem, though. Much appreciated, and gives a good feeling about the product, which I’m obviously still using, though in a different hosting environment.