• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Wordpress Toolkit: Critical error while checking for updates

Katog Choling

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
Plesk Obsidian v18.0.57_build1800231218.09
In the Plesk control panel for my site, the WP Toolkit is reporting this critical error whenever it checks for updates on my wordpress site. Curiously, this error doesn’t seem to happen when I check for updates manually from the WordPress Updates dashboard page. Any thoughts on what might be happening?

Failed to reset cache for the instance #1: PHP Fatal error: Cannot declare class WP_Rollback_API_Fetcher, because the name is already in use in /var/www/vhosts/mywebsite/wp-content/plugins/wp-rollback/src/class-rollback-api-requests.php on line 2
Fatal error: Cannot declare class WP_Rollback_API_Fetcher, because the name is already in use in /var/www/vhosts/mywebsite/wp-content/plugins/wp-rollback/src/class-rollback-api-requests.php on line 2
Error: There has been a critical error on this website.
 
The error comes as the Toolkit does more checks than WP itself before updates, in this case you have plugins using classes that already exist/used.
I would recommend checking the wp-rollback plugin (from the error)
 
Back
Top