markmakershannon

@yorman This is still an issue for me.

I cannot upgrade from Version 1.7.17 to Version 1.8.1 (WordPress version-4-5-3)

Cannot redeclare class SucuriScanSiteCheck in /var/www/wp-content/plugins/sucuri-scanner/sucuri.php on line 13555

Steps tried

• Upgrade from WordPress not working
• FTP into plugins and removing, then re-downloading

[Mon Sep 12 12:09:05.941660 2016] [:error] [pid 1079] [client (MY IP ADDRESS):39955] PHP Fatal error:  Cannot redeclare class SucuriScanSiteCheck in /var/www/wp-content/plugins/sucuri-scanner/sucuri.php on line 13555, referer: https://(WEBSITE HOST IP)/wp-admin/update.php?action=upgrade-plugin&plugin=sucuri-scanner%2Fsucuri.php&_wpnonce=1ce6c4ca46
[Mon Sep 12 12:09:13.605022 2016] [:error] [pid 1078] [client (MY IP ADDRESS):39958] PHP Fatal error:  Cannot redeclare class SucuriScanSiteCheck in /var/www/wp-content/plugins/sucuri-scanner/sucuri.php on line 13555, referer: https://(WEBSITE HOST IP)/wp-admin/plugins.php
[Mon Sep 12 12:09:17.441074 2016] [:error] [pid 1747] [client (MY IP ADDRESS):39959] PHP Fatal error:  Cannot redeclare class SucuriScanSiteCheck in /var/www/wp-content/plugins/sucuri-scanner/sucuri.php on line 13555, referer: https://(WEBSITE HOST IP)/wp-admin/update.php?action=upgrade-plugin&plugin=sucuri-scanner%2Fsucuri.php&_wpnonce=1ce6c4ca46
[Mon Sep 12 12:09:20.844874 2016] [:error] [pid 1081] [client (MY IP ADDRESS):39964] PHP Fatal error:  Cannot redeclare class SucuriScanSiteCheck in /var/www/wp-content/plugins/sucuri-scanner/sucuri.php on line 13555, referer: https://(WEBSITE HOST IP)/wp-admin/update.php?action=upgrade-plugin&plugin=sucuri-scanner%2Fsucuri.php&_wpnonce=1ce6c4ca46
[Mon Sep 12 12:09:43.618734 2016] [:error] [pid 1079] [client (WEBSITE HOST IP):60582] PHP Fatal error:  Cannot redeclare class SucuriScanSiteCheck in /var/www/wp-content/plugins/sucuri-scanner/sucuri.php on line 13555

• This reply was modified 8 years, 5 months ago by markmakershannon.
• This reply was modified 8 years, 5 months ago by markmakershannon.

@yorman

Thanks for the reply, and explanation. The most recent development version seems to have worked sucessfully. Is this fix rolled out in the most recent version of the plugin?