Is there a known compatibility issue?
Not that I’m aware of; this is the first I’ve heard of an issue with this plugin.
Thread Starter
anonymized-11892634
(@anonymized-11892634)
Hey Kevin,
I was able to get it working by removing the check for DOING_CRON.
Just wondering, will that cause any big issues? I’m guessing that check was put in place to stop the cron being redirected to the login page?
Phil
Thread Starter
anonymized-11892634
(@anonymized-11892634)
Looks like https://github.com/Automattic/WP-Cron-Control/blob/master/wp-cron-control.php#L319 may be the cause.
Would it be possible for you to adapt the FL plugin to work with this? I appreciate you may not want to, in which case I’ll use another option. Just wanted to check as I prefer using the FL plugin if possible.
Hi Phil,
Thanks for investigating this further; I’ve addressed your questions below:
I’m guessing that check was put in place to stop the cron being redirected to the login page?
Yes, that conditional statement was to ensure Cron tasks would be able to run without interference from Force Login. Without it, some other plugins like Wordfence might not be able to work properly.
Would it be possible for you to adapt the FL plugin to work with this?
I don’t believe removing the DOING_CRON conditional check will be an option; as that may break how Force Login works with other plugins. However, I am considering another change to FL that may resolve this issue, but I can’t be sure until we test it.
I’ll let you know when I’ve released a new version for you to try.
Thanks!
Hi Phil,
It looks like the WP Cron Control plugin author is aware of this issue and is working on fixing it:
https://github.com/Automattic/WP-Cron-Control/issues/4
