Robert

Indeed we are thanks Jeff. And we have discovered there is a known conflict between TML and WordPress when activating 2FA – as we had indeed been testing out. Thank you for getting back. I understand there’s currently no fix available.

In WordPress 6.1 extra error reporting was added so previously unseen errors are now logged and the following appeared on the Error Log Monitor on PROD. The author of WP Crontol recommended setting the error to ‘Ignore’.

‘Ignoring” the error in Error Log Monitor did not always record the error correctly as ignored and the error continued to be reported. The author of Error Log Monitor recommended that, if this happens, add the error or the part of it that keeps repeating to the “Ignored regular expressions” setting.

Hope this helps.

Cheers

Robert

Thanks Adam. Most helpful. We do a full forced recheck of all BLC links every 6 months or so and we’re due to do that in a couple of weeks time. So hopefully that will solve the problem. Will let you know if the problem continues after that. Your help and advice is much appreciated. Cheers Robert

Thanks for getting back Patrick. However, that’s not the problem. The /wpmembers/ folder is already in the BLC exclusion list. Any other thoughts on what the problem could be? Many thanks – Robert

Thanks very much Kris for getting back. Files are uploaded using cPanel file manager and then linked from there. The files are stored in a subfolder of the /uploads/ folder with restricted access using the Prevent Direct Access plugin. The full path for these meeting minutes is https://one-name.org/wp/wp-content/uploads/wpmembers/trustees/minutes/20221212/Trustee%20Minutes%2012%20December%202022.pdf However, you need to be logged in as a Guild member to view them.
We’ve been doing this for over a year now without any problem until very recently.

Thank you Peter. Most helpful advice.

I found three different blc events. Kept deleting them until I got the following message:
The cron event blc_cron_check_links could not be found
The cron event blc_cron_email_notifications could not be found
The cron event blc_cron_database_maintenance could not be found

All three were immediately regenerated. Will let you know if that fixes the PHP Error notification problem.

Thanks heaps Patrick. Will try that and let you know.

Cheers

Robert

Thanks very much for responding. Here’s the full error:

[10-Dec-2022 21:26:11 UTC] Cron reschedule event error for hook: blc_cron_check_links, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”10min”,”args”:[],”interval”:600}

Thank you so very much John. A really helpful reply. So based on your reply, I assume we can set the PHP Errors being displayed by the plugin Error Log Monitor [and are cluttering up our Dashboard] to ‘Ignore’ but leave the errors in the error log itself for reference if needed?

Thanks Janis. Will give that a go.
Robert

Thanks very much for your reply. However, all the notifications look exactly the same to me. Here’s a sample:

Dec 08, 02:56:40
Cron unschedule event error for hook: members_admin_notifications_update, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]}

Dec 08, 03:02:11
Cron unschedule event error for hook: members_admin_notifications_update, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]}

Dec 08, 03:26:51
Cron unschedule event error for hook: members_admin_notifications_update, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]}

Dec 08, 05:06:08
Cron unschedule event error for hook: members_admin_notifications_update, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]}

Dec 08, 05:09:42
Cron unschedule event error for hook: members_admin_notifications_update, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]}

Dec 08, 06:26:40
Cron unschedule event error for hook: members_admin_notifications_update, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]}

Dec 08, 09:39:40
Cron unschedule event error for hook: members_admin_notifications_update, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:false,”args”:[]}`

Thank you. Will do.

We also use the Members plugin and getting the same error in the PHP Error Log on the Dashboard multiple times every day. This clutters up the log and makes it difficult to spot real errors. These errors only started happening after we installed the WP 6.1.1 update.

So can I delete it using WP Crontrol? I don’t think it’s working anyone. If I try and edit it in WP Crontrol, I get a message ‘The event you are trying to edit does not exist.’

Many thanks
Robert

Thanks to you both for your suggestions. The errors are being reported in the PHP Error Log and displayed in the WordPress Dashboard. They are repeating each day.

I had missed the possible reference to WordFence. Will check that out.

Our PHP version has not changed. We are still using 7.4.

We are not getting these errors on our development site that has exactly the same version of WP installed. It was installed a week earlier when WP was still 6.1 and not 6.1.1. Our development site has now been auto updated to 6.1.1.

I gather from your responses that this error is peculiar to our setup and not a more general problem.

Thanks again for your help.

Cheers

Robert