Critical error after 2.0.1 Update
-
Hello,
I was pleased that there was an update after a long time.
But does it generate a critical error when I deactivate it?
The following is the error message;
When seeking help with this issue, you may be asked for some of the following information: WordPress version 6.0 Active theme: xxx Child Theme (version 4.9) Current plugin: APG Google Image Sitemap Feed (version 2.0.1) PHP version 8.0.3 Error Details ============= An error of type E_ERROR was caused in line 41 of the file /var/www/vhosts/xxx.de/xxx/wp-content/plugins/google-image-sitemap-feed-with-multisite-support/includes/admin/clases/xml.php. Error message: Uncaught TypeError: count(): Argument #1 ($var) must be of type Countable|array, bool given in /var/www/vhosts/xxx.de/xxx/wp-content/plugins/google-image-sitemap-feed-with-multisite-support/includes/admin/clases/xml.php:41 Stack trace: #0 /var/www/vhosts/xxx.de/xxx/wp-includes/class-wp-hook.php(307): APGSitemapImage->rewrite() #1 /var/www/vhosts/xxx.de/xxx/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters() #2 /var/www/vhosts/xxx.de/xxx/wp-includes/plugin.php(524): WP_Hook->do_action() #3 /var/www/vhosts/xxx.de/xxx/wp-includes/class-wp-rewrite.php(1458): do_action_ref_array() #4 /var/www/vhosts/xxx.de/xxx/wp-includes/class-wp-rewrite.php(1488): WP_Rewrite->rewrite_rules() #5 /var/www/vhosts/xxx.de/xxx/wp-includes/class-wp-rewrite.php(1859): WP_Rewrite->wp_rewrite_rules() #6 /var/www/vhosts/xxx.de/xxx/wp-content/plugins/google-image-sitemap-feed-with-multisite-support/apg-xml-sitemap.php(41): WP_Rewrite->flush_rules() #7 /var/www/vhosts/xxx.de/xxx/wp-includes/class-wp-hook.php(307): apg_image_sitemap_actualiza() #8 /var/www/vhosts/xxx.de/xxx/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters() #9 /var/www/vhosts/xxx.de/xxx/wp-includes/plugin.php(476): WP_Hook->do_action() #10 /var/www/vhosts/xxx.de/xxx/wp-admin/includes/class-plugin-upgrader.php(371): do_action() #11 /var/www/vhosts/xxx.de/xxx/wp-admin/update.php(51): Plugin_Upgrader->bulk_upgrade() #12 {main} thrown
Best regards
Torsten
Viewing 2 replies - 1 through 2 (of 2 total)
Viewing 2 replies - 1 through 2 (of 2 total)
- The topic ‘Critical error after 2.0.1 Update’ is closed to new replies.