SuttsQ: Plugin (free version) causing critical error after update to 4.0.18 and 4.0.19
I've had this plugin sitting in my basket for a while as I love the concept. Generally on simple sites it works really well. I've been using the free version on 3 different WordPress sites on 3 different hosts and was happy with the results.
However, after upgrading the plugin to 4.0.18 yesterday, it caused a critical WordPress error on 2 of the sites, so obviously I didn't update the third. Today I checked and saw version 4.0.19 had been released. Assuming that included a fix, I upgraded the plugin on the last site, however it again caused a critical error!
I didn't want to leave a bad review as the plugin is great, when it works! But if I can't trust a plugin not to break a site on a small update, then I can't use it on production websites.
Has anyone else reported this issue? If so, do you have a fix?
Hamza_Mairaj
May 20, 2026A: Hey there,
It’s not like the error is embedded in the plugin, there must be some conflict. Could you please create a support ticket with WordPress login details for any website that encountered the error so we investigate this further? If you need help recovering the website, we can help with that too.
Hi Hamza, thanks for your reply. I appreciate the error isn't embedded in the plugin, however the only way to recover the sites was to deactivate the plugin itself. A conflict makes sense, elementor maybe? Sorry, I should have noted down the error, I just tried to replicate it but it won't let me reactivate it with the message, "Plugin could not be activated because it triggered a fatal error."
Can’t say for sure what caused it. If you could share the WordPress login details, we’ll be able to investigate the cause and fix the error.
Thanks Hamza, appreciate that. However as these were on production sites I've resolved it by deactivating the plugin. Although now it won't let me delete the plugin, I get the message, "Deletion failed: There has been a critical error on this website.Learn more about troubleshooting WordPress." If I have time, I'll fire up a test site to see if I can replicate it.
A test site would be even better
Hamza, here is the error from the logs and the contents of the advanced-cache.php file that was causing the issue: https://pastecode.io/s/vhbxvj77
I hope that helps! If I get time to create a test site I'll raise a ticket directly, rather than clogging up AppSumo!
It looks like the plugin directory was manually deleted or renamed. In that case, the advanced-cache.php file also needs to be removed manually otherwise it can trigger a critical error.
The error log confirms that the code cannot find the plugin directory because it has been renamed or deleted.
If it's easier, we can continue the discussion at [email protected].