sneader

I’ve seen this “Error There has been a critical error on your website” problem on two WP sites in the last 12 hours. Removing the Wordfence directory from /wp-content/plugins/ brings the site back up and running. Nothing is logged in error_log.

– Scott

Just jumping on the bandwagon… we provide hosting services and one of our clients had a site that also went into a death spiral. He said he only updated two plugins before it happened, and yours was one of them. We removed the plugin via command line and it brought the site back up and running. Clearly 1.11.13 has a serious issue. I’m glad that @agathongroup was able to capture so much information to assist you.

– Scott

It appears that EWWW has the option to resize the hi-res originals that WP has stored after scaling… any chance you will bring that feature to Imsanity?

I just installed 3.5.2 from repo as a new plug-in (i.e. not updating the plugin, installing it on a new site) and the checkboxes are not working.

– Scott

Doing further research, it appears that the form is requiring a radio button field to have an item chosen, even though it is NOT a required field.

This may be an unintended bug in CF7 that needs to be reviewed.

– Scott

Same problem here. I’m a little worried that the author does not seem to be providing support here any longer, as your question and others are left unanswered.

– Scott

Thanks, Ian. I’m super disappointed, since the plugin works so well. Is it possible to update the plugin by downloading the .zip from the other repo, and just upload it on top of the existing one, or do we have to start over from scratch?

There are really no other good plugins like this, for free. When we work with small organizations on limited budgets, your plugin was our go-to. You did good work while it lasted, and I thank you for that!

– Scott

I found the answer. Under Menus > Settings > Basic > Style, there is an On/Off switch “Display Section Descriptions” — turning on that switch solved the problem!

– Scott

@macmanx In every situation (in our standard cPanel-based hosting environment), there is no persistent error. The upgrade to v8 completes fine EXCEPT this silly email that is sent to customers with the subject “Your Site is Experiencing a Technical Issue” — note that it is clearly indicating there IS a problem, not there was, or could be.

The email goes on to tell customers to check their site for any visible issues, then to “Please contact your host for assistance with investigating this issue further.”

All for nothing, because there is no problem!

When customers open tickets for help (because WP’s email tells them to do that), we just tell customers it is a bug with the Jetpack upgrade, generating a false alert, and to ignore it.

However, this is diminishing the value of the “Technical Issue” email notifications from WordPress, as now customers do not know whether to take them seriously or not.

This seems preventable and ought to get resolved.

– Scott

As a hosting provider, this is a horrible issue. This error occurs EVERY TIME someone upgrades Jetpack from version 7 to 8, and the email you send the user, even though nothing is actually wrong, says “Please contact your host for assistance with investigating this issue further.”

Can this really not be fixed?

– Scott

I can confirm that I can fix the issue by enabling the pdo_mysql extension.

– Scott

@asyag I did a search in the WordPress database for the bad path, found it, and fixed it to be the correct path, so I no longer need support.

– Scott

Yes, problem still exists in 3.37.1. For db server, it is 10.1.41-MariaDB. I have created a phpinfo for you, and printed to a PDF file, and shared via Google Drive:

https://drive.google.com/file/d/1xqJ5ZQafTpVJnVkuQCa-56YlCLDFEEKi/view?usp=sharing

FYI, I am the root server owner, so if there is any other info I can help with, let me know.

– Scott

The problem continues, but now the printed error on the page says:

string(63) "/home/baduser/public_html/subdir/wp-content/uploads/photo-gallery"

The directory should be /home/gooduser/public_html/wp-content/uploads/photo-gallery. We need to correct the username and also there is no subdir. How can I do this? Where is this bad username and upload path coming from? Where is it stored?

– Scott

This was very helpful. The dump showed a very strange path (/home/baduser/public_html/subdir/wp-content…) where the path is actually /home/gooduser/public_html/wp-content…)

Do I need to try to find this path in the database? Where is it pulling this weird/bad path from?

– Scott