alexDx

The fact that this is still an issue is just sad. There really is no excuse for it. I still have to perform these ridiculous workarounds to get things to work on the sites I still use this plugin on. The developers should be ashamed.

Almost a year later and this is still an issue. I have to go through a workaround on every single staging/development site.

8 months later, issue is still happening. Come on guys … this is ridiculous.

This error kept happening even after completely moving to another host, deactivating all plugins and activating a default WordPress theme. Its obvious at this point that Wordfence was the issue.

I removed Wordfence entirely and decided to go with: https://ww.wp.xz.cn/plugins/better-wp-security/

Will be using this plugin on our 300 websites.

Also, The error is still there after I deactivated all plugins and switched the theme to a default one.

Just an update here that this is still an issue. We have to run through this: https://yoast.com/help/how-to-reset-yoast-indexables/ on every single staging site where we update any SEO. Its a HUGE pain to do this.

yes I mentioned it was not working above. …

Hi, I have followed these steps, but I’m still seeing the logs being written to.

Example site: https://adamstonvet.com/

I cleared out the wp_eum_logs table

I’ve created a new mu-plugin with the following code:

<?php
function eum_disable_logs($value) {
if (!is_array($value)) $value = array();
if (empty($value['core']) || !is_array($value['core'])) $value['core'] = array();
$value['core']['logs'] = 'off';
return $value;
}
add_filter('pre_update_site_option_MPSUM', 'eum_disable_logs', 10);
add_filter('pre_update_option_MPSUM', 'eum_disable_logs', 10);

I’ve uploaded this as eum_disable_logs.php to /wp-content/mu-plugins directory on 7/2/2024.

Cleared server cache, then clicked on a setting in the Updates settings section.

Still seeing plugin updates logged to the table ….