SIte crash after update

Looking at the error, it appears that WordPress did not download/install the plugin update successfully as the latest version is 4.4.0 and the methods referenced in the error do not exist in v4.4.0.

Were you updating Site Reviews normally from the Plugins or the WordPress updates page?

Hi,
I updated from Version 4.2.9 from the WordPress update page “../wp-admin/update-core.php”.
It downloaded the new version, site crashed, then plugin got deactivated by WP.

Now if I try to activate the following message appears: Plugin could not be activated because it triggered a fatal error. The error is the same as written before.

In plugins page it says is Version 4.4.0

Screenshot: https://imgur.com/0UeiGnZ

• This reply was modified 4 years, 9 months ago by yano23. Reason: added screenshot

Hmm, I’m not sure what caused this as I have not heard of this particular issue before.

However, you can fix this by deleting the Site Reviews plugin (your reviews are safe, however you will lose your plugin settings and any custom translations you had). Once you have removed the plugin, reinstall and activate it.

I will be looking further into this issue…

Hi,

I don’t know why, because I haven’t made any changes since last night, but today the plugin works.

Thanks for the prompt support!

I’ve also seen crashes on three separate sites when upgrading the plugin. I upgraded from version 3.5.2 to 4.4.0 in all instances. Here is output from one of the WordPress error emails:

WordPress version 5.3.2
Current plugin: Site Reviews (version 4.4.0)
PHP version 7.1.33-3+ubuntu16.04.1+deb.sury.org+1

Error Details
=============
An error of type E_ERROR was caused in line 22 of the file /www/wp-content/plugins/site-reviews/plugin/Modules/Upgrader.php. Error message: Uncaught UnexpectedValueException: DirectoryIterator::__construct(/www/wp-content/plugins/site-reviews/plugin/Modules/Upgrader): failed to open dir: No such file or directory in /www/wp-content/plugins/site-reviews/plugin/Modules/Upgrader.php:22
Stack trace:
#0 /www/wp-content/plugins/site-reviews/plugin/Modules/Upgrader.php(22): DirectoryIterator->__construct(‘/www/wp-content…’)
#1 /www/wp-content/plugins/site-reviews/plugin/Application.php(264): GeminiLabs\SiteReviews\Modules\Upgrader->run()
#2 /www/wp-content/plugins/site-reviews/plugin/Application.php(279): GeminiLabs\SiteReviews\Application->upgrade()
#3 /www/wp-includes/class-wp-hook.php(288): GeminiLabs\SiteReviews\Application->upgraded(Object(Plugin_Upgrader), Array)
#4 /www/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters(”, Array)
#5 /www/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
#6 /www/wp-admin/includes/class-plugin-upgrader.php(316): do_action(‘upgrader_proces…’, Object(Plugin_Upgrader), Array)
#7 /www/wp-admin/update.

@loganstrike

Did the plugin work fine after the crash after upgrading each time?

I will have this fixed in the next update.

@yano23 @loganstrike

I have tried countless times to duplicate this issue without success. It may have something to do with the setup of your server or the way it handles server-side caching when WordPress performs updates.

However, I believe I have fixed it in v4.5.0 which will be released in the next day or two.

If you are interested, here is the fix:

https://github.com/pryley/site-reviews/blob/master/plugin/Modules/Upgrader.php
https://github.com/pryley/site-reviews/blob/master/plugin/Modules/Upgrades/index.php

@geminilabs

The plugin seemed to work fine after the upgrade errors, but I didn’t look too deeply because the sites were all in development and I reinstalled the plugin to be sure.

We have version 3.5.2 saved in an older Flywheel blueprint so I can reproduce the error at will. After applying the above fixes and running the upgrade, I received no errors.

@loganstrike

Great! Thanks for testing.