• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs Wordpress Toolkit Error when Scanning for Updates

G J Piper

Regular Pleskian
Username:

TITLE

Wordpress Toolkit Error when Scanning for Updates

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Wordpress Toolkit 5.9.1-5836, PHP 8.1.2, Plesk 18.0.41, CentOS 7.9.2009, Nginx 1.20.2, Apache 2.4.6, MySQL 10.6.5-MariaDB

PROBLEM DESCRIPTION

Running Wordpress Toolkit results in error messages for each site scanned for updates. The site scans appear to result in accurate update listings, but the PHP errors are spit out at the end.

STEPS TO REPRODUCE

Install some Wordpress sites on appropriate hardware and software. Load the latest Wordpress Toolkit. Scan for updates to the wordpress sites on "all sites".

ACTUAL RESULT

This is the error listed for each site scanned:

Code:
Failed to reset cache for the instance #14: PHP Fatal error:  Uncaught Error: Call to a member function setAllowedTags() on null in /var/www/vhosts/samplewebsite.com/httpdocs/wp-content/plugins/svg-support/functions/attachment.php:246
Stack trace:
#0 /var/www/vhosts/samplewebsite.com/httpdocs/wp-includes/class-wp-hook.php(307): bodhi_svgs_apply_filters()
#1 /var/www/vhosts/samplewebsite.com/httpdocs/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#2 /var/www/vhosts/samplewebsite.com/httpdocs/wp-includes/plugin.php(474): WP_Hook->do_action()
#3 /var/www/vhosts/samplewebsite.com/httpdocs/wp-settings.php(565): do_action()
#4 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1291): require('...')
#5 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1212): WP_CLI\Runner->load_wordpress()
#6 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(23): WP_CLI\Runner->start()
#7 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(77): WP_CLI\Bootstrap\LaunchRunner->process()
#8 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap()
#9 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php(17): require_once('...')
#10 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php(31): require_once('...')
#11 {main} thrown in /var/www/vhosts/samplewebsite.com/httpdocs/wp-content/plugins/svg-support/functions/attachment.php on line 246
Fatal error: Uncaught Error: Call to a member function setAllowedTags() on null in /var/www/vhosts/samplewebsite.com/httpdocs/wp-content/plugins/svg-support/functions/attachment.php:246
Stack trace:
#0 /var/www/vhosts/samplewebsite.com/httpdocs/wp-includes/class-wp-hook.php(307): bodhi_svgs_apply_filters()
#1 /var/www/vhosts/samplewebsite.com/httpdocs/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#2 /var/www/vhosts/samplewebsite.com/httpdocs/wp-includes/plugin.php(474): WP_Hook->do_action()
#3 /var/www/vhosts/samplewebsite.com/httpdocs/wp-settings.php(565): do_action()
#4 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1291): require('...')
#5 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1212): WP_CLI\Runner->load_wordpress()
#6 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(23): WP_CLI\Runner->start()
#7 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/bootstrap.php(77): WP_CLI\Bootstrap\LaunchRunner->process()
#8 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap()
#9 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/vendor/wp-cli/wp-cli/php/boot-fs.php(17): require_once('...')
#10 /usr/local/psa/admin/plib/modules/wp-toolkit/vendor/wp-cli/wpt-wp-cli.php(31): require_once('...')
#11 {main} thrown in /var/www/vhosts/samplewebsite.com/httpdocs/wp-content/plugins/svg-support/functions/attachment.php on line 246
Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.

EXPECTED RESULT

Clean scan without PHP errors.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
I just realized the Wordpress Toolkit might just be running on the installed PHP 7 version I have: 7.4.27
All the websites are running 8.1.2
 
It appears the "SVG Support" plugin has been updated to avoid throwing the CLI errors now.
Still, it might be a good thing if the toolkit had its own checks to make sure that couldn't happen too though.

 
From developer:

The issue is on "SVG Support" side. Plugin ''SVG Support" version 2.4 is not compatible with wp-cli. They fixed the issue in version 2.4.1:
Version 2.4 breaks WP-CLI

To fix the issue:
Update the plugin to the latest version. If it's not possible to update plugin using WPTK(due to plugin incompatibility with "wp-cli" ) then login to WordPress admin dashboard using direct link https://samplewebsite.com/wp-login.php and update "SVG Support" to the latest version.

Another solution - remove ''SVG Support" 2.4 using WPTK and install latest "SVG Support" version.
 
Back
Top