Fatal error: Uncaught Error: NoticeController.php

Hi @zevs3000,

Can you please tell us what happens if you completely remove our plugin (deactivate + remove) and then you re-install it? Does the issue get solved?

Best,

yes, I uninstalled it, even deleted 2 DB records. then install it back and when I try to activate the plugin I`m getting the error

The quickest way to fix this is download the repo from Shortpixel Repo and replace the content within the plugin folder.

I get the same error (see below)

PHP 7.3.19
Wordpress 5.4.2
ShortPixel 4.19.2

Yes I’ve uninstalled and reinstalled the plugin. I’ve tried reverting to 4.18.1. I’ve also tried downloading from the ShortPixel repo and replacing the content in the plugin folder. Tried deactivating all plugins and just activating ShortPixel. None of it works.

Fatal error: Uncaught Error: Call to undefined method stdClass::getID() in /home3/tillmanc/public_html/wp-content/plugins/shortpixel-image-optimiser/build/shortpixel/notices/src/NoticeController.php:185 Stack trace: #0 /home3/tillmanc/public_html/wp-content/plugins/shortpixel-image-optimiser/class/Controller/AdminNoticesController.php(56): ShortPixel\Notices\NoticeController::removeNoticeByID(‘Error100’) #1 /home3/tillmanc/public_html/wp-content/plugins/shortpixel-image-optimiser/shortpixel-plugin.php(376): ShortPixel\Controller\AdminNoticesController::resetCompatNotice() #2 /home3/tillmanc/public_html/wp-includes/class-wp-hook.php(287): ShortPixel\ShortPixelPlugin::activatePlugin(”) #3 /home3/tillmanc/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(”, Array) #4 /home3/tillmanc/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array) #5 /home3/tillmanc/public_html/wp-admin/plugins.php(179): do_action(‘activate_shortp…’) #6 {main} thrown in /home3/tillmanc/public_html/wp-content/plugins/shortpixel-image-optimiser/build/shortpixel/notices/src/NoticeController.php on line 185

• This reply was modified 4 years, 8 months ago by shackadeli.
• This reply was modified 4 years, 8 months ago by shackadeli.

Solving this conversation. User @shackadeli had a strange database error which will be fixed in future versions of SPIO.