miku0010

The error is generated by a CLI call of cron.php with the following err-message: “<!– simplehtmldom failed to process the html –>”

I hope that helps.

This is a technical IONOS (1&1) problem.
Same problem on one of our customer servers.

We have check the SFTP-Log and identify an user named “sitelock-********” means the IONOS Sitelock-Product write these crap-files. Tech support told me to delete the files myself and they were from the IONOS software.

Regarding the point that files are now constantly being generated, the Tech support said… that’s just the way it is. It is IONOS.

Hallo Support-Team,

Wir hatten auch ein “critical error” gestern Nacht nach dem Update auf 3.0.1.
Kunden Website + Shop war nicht mehr erreichbar.

Wordpress Version 6.0.1
WooCommerce Version 6.7.0

Debug Log:

[26-Jul-2022 01:00:59 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function wp_get_current_user() in /var/www/vhosts/REMOVED/httpdocs/wp-includes/capabilities.php:693
Stack trace:
#0 /var/www/vhosts/REMOVED/httpdocs/wp-includes/functions.php(3533): current_user_can()
#1 /var/www/vhosts/REMOVED/httpdocs/wp-includes/formatting.php(2061): get_allowed_mime_types()
#2 /var/www/vhosts/REMOVED/httpdocs/wp-content/plugins/woorechnung/woorechnung.php(44): sanitize_file_name()
#3 /var/www/vhosts/REMOVED/httpdocs/wp-content/plugins/woorechnung/woorechnung.php(78): fp_sanitize_path()
#4 /var/www/vhosts/REMOVED/httpdocs/wp-content/plugins/woorechnung/woorechnung.php(104): user_home_path()
#5 /var/www/vhosts/REMOVED/httpdocs/wp-settings.php(428): include_once('/var/www/vhosts...')
#6 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1291): require('/var/www/vhosts...')
#7 /usr/local/psa/ in /var/www/vhosts/REMOVED/httpdocs/wp-includes/capabilities.php on line 693

fyi

I have uninstalled iThemes Security Plugin and if the changes no longer occur I can assume that iThemes Security caused them.

Next i will uninstall iThemes Security on all client sites since the plugin performs this strange behavior.

No one provided me with an answer to this.
This shows me that this function is not normal.

Thanks for fix. But fatal errors like these aren’t usefull. I will change the update procedure on all of my wp-pages again but i have removed this plugin from all pages.

So it depends on the time of the backup.
That concerns many Plugins.

Is there a WP-Database flag/var in WordPress that is set “true” when plugins “do their things”, so that WordPress doesn’t start internal core or plugin updates?

Could you (or the Inpsyde GmbH) report this problem to WordPress as developer?

Thanks a lot!
Michael

Same here.

Thanks for the plugin! Support is always time consuming for free plugins.

Maybe you can find a solution for this WPML problem? I currently have same problem as described here.

All other features of the plugin work fine.

Thanks a lot.