cordschneider
Forum Replies Created
-
@leogc It worked for me too. Although that said, having been through this experience I’ve opted to switch to using Google Analytics for most of the sites that we manage.
Same error here:
Post SMTP (version 2.0.20) PHP version 7.4.14 Error Details
=============
An error of type E_ERROR was caused in line 19 of the file /var/www/httpdocs/www/wp-content/plugins/post-smtp/Postman/Extensions/Admin/PostmanAdmin.php. Error message: Uncaught Error: Class ‘PostmanViewController’ not found in /var/www/httpdocs/www/wp-content/plugins/post-smtp/Postman/Extensions/Admin/PostmanAdmin.php:19Stack trace:
#0 /var/www/httpdocs/www/wp-includes/class-wp-hook.php(287): PostmanAdmin->add_menu()
#1 /var/www/httpdocs/www/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters()
#2 /var/www/httpdocs/www/wp-includes/plugin.php(484): WP_Hook->do_action()
#3 /var/www/httpdocs/www/wp-admin/includes/menu.php(155): do_action()
#4 /var/www/httpdocs/www/wp-admin/menu.php(327): require_once(‘/var/www/vhosts…’)
#5 /var/www/httpdocs/www/wp-admin/admin.php(158): require(‘/var/www/vhosts…’)
#6 /var/www/httpdocs/www/wp-admin/plugin-install.php(16): require_once(‘/var/www/httpdocs…’)
#7 {main} thrownI agree with @erlendeide; a plugin should never run this kind of database optimisation. Not in the foreground. Not in the background. Not ever.
If there is a valid reason to perform such a database optimisation – perhaps because of data structure changes etc. – then as developers you should let your users know the reasons for doing the optimisation and what exactly they should do post the upgrade. The rest should be up to them to decide if and when they wish to follow your advice.
I have experienced exactly the same thing, causing my client’s website to timeout with a 503 error. Monitoring the currently active processes, I can see HTTP queries queuing waiting on the database locks to free up.
I have disabled WP Statistics for now as it renders the website useless.
I have exactly the same issue with the GDPR Cookie Compliance dialog being shown in the Gutenberg editor when Oxygen is installed. It seems to be related to the Oxygen Gutenberg Integration plugin as when I deactivate that, the GDPR Cookie Compliance dialog no longer shows up in Gutenberg.
I have tried the code snippet above but it seems that it doesn’t work as long as the Oxygen Gutenberg Integration is activated. Any thoughts as to what else can be done?