Hi @mossifer
I’m so sorry to hear you’ve run into a fatal error! I know how stressful it is to see your site go down, and I really appreciate you digging into the code to find the specific line causing the trouble.
The line you commented out is a safety check that “throws” an error when a database query fails. While commenting it out lets the site load, it hides an underlying database issue that we still need to fix.
I have encountered a very similar ticket in the past where this specific error was triggered by an outdated database environment. Often, when the MySQL or MariaDB version on the server is older, it struggles to process some of the modern database queries used by current versions of Kadence Blocks.
Check the detailed information about https://make.ww.wp.xz.cn/hosting/handbook/server-environment/#database
Could you please confirm your MySQL version and other relevant server details? You can usually find this in your WordPress dashboard under Tools > Site Health > Info > Database.
For closer look at your setup, you can also submit the support ticket via these channels:
Looking forward to helping you get this resolved!
Best regards,
Archita
If this is bringing down sites, then you need to check IN THE CODE if the database has DELETE/ALTER rights and if not, then don’t execute that line. It’s up to the developer to put in these checks.
Hey @mossifer ,
Thanks for sticking with us on this, and I want to step in to clarify exactly what is happening under the hood. First, you are completely right: our plugin should never bring down your site.
We have reviewed this and logged an official bug report with our development team. Here is the breakdown of what is happening and how we are fixing it:
- You are 100% correct that we need to prevent this crash. We should be try-catching the error gracefully if the server denies the request. Our developers are working on an update so that if a database lacks these permissions, the plugin will no longer throw a fatal error.
- That being said, the Optimizer does need those structural permissions (
DELETE, ALTER, and DROP) to actually do its job and manage its tables (like kb_optimizer_viewport_hashes). Because your environment is actively blocking those standard commands, the process is failing.
Overall, a fatal error isn’t the way you should find out about the need of these database permissions.
While we work on improving the error handling on our end so it doesn’t crash the site, you will still need those permissions to actually use the Optimizer. To safely uncomment that line in your files and get everything working, you should update your database user to ensure it has standard DELETE, ALTER, and DROP privileges.
I hope this helps. If you’d like to track the progress of this bug, you can reach out directly to us here.
Best regards,
Victor
