Critical site error after update

The FTP upload / unzip worked for me as well – Running PHP 7.3.12
What’s odd is that I’m running this on other sites with the exact same plugins / server etc and it worked fine there.

@simplecalendarsupport – I don’t, but my supervisor does. I’ll see if he can help me complete this step and let you know how we do.
Thank you,
Jen

@simplecalendarsupport I’m running PHP 7.3+ (per https://wordpress.org/support/topic/critical-site-error-after-update/#post-13358537) and I specifically removed the plugin from the site admin and re-installed it using FTP (per https://wordpress.org/support/topic/critical-site-error-after-update/#post-13358592).

Seems this is related to certain hosting setups not extracting the plugin fully during update/install considering all that needed to be done for myself & @sflwa was to just install via FTP instead of via the site admin (only difference being we know the FTP upload completed 100% whereas using the site admin must’ve left some files incomplete/missing.)

What else could it be considering it’s the same version being updated/uploaded (one just via the site admin vs. the other doing so via FTP)?

FYI, the site I was working with is on GoDaddy-based hosting, and probably one of their cheaper (if not cheapest) plans. Maybe there are too many files needing to be extracted and the process hits a timeout limit that stops the important update/install process too early due to an insufficient/bad hosting setup and/or hiccup…? What else would cause a plugin update/install to stop too early / leave it partially extracted/implemented?

My hosting is specifically the Managed WordPress offered by GoDaddy (again, probably the cheapest offering available for that service through GoDaddy.) So the control over server settings, WordPress configurations, etc. are more limited than other hosting options (wasn’t my choice to have them host with this setup, for what its worth.) Here are the extended set of server & database details, if they happen to be helpful in any way: https://gist.github.com/KZeni/570d704ce1d6fe4273196b3f276f9d66

So we’ve confirmed it’s been with GoDaddy’s Managed WordPress (per myself & @sflwa) hosting and SiteGround Shared Hosting (per https://wordpress.org/support/topic/critical-site-error-after-update/#post-13358577) thus far and it’s inconsistent across multiple sites using similar hosting setups while uploading via FTP seems to fix the experienced issue for everyone that has reported as trying it.

Curious why GoDaddy’s Managed WordPress hosting & SiteGround Shared Hosting experienced and/or is experiencing this issue. Are they just under-powered hosting environments for what this plugin needs during update/extraction? A hiccup seems odd since it happened to SiteGround and GoDaddy hosted sites (seems unlikely they both had a hiccup at the time of the plugin update.)

@mgc Definitely sounds like it’s running into a timeout limit with your hosting which then leaves the plugin in a broken state (as it appears everyone else here has been running into.)

Any luck with uploading the current version with (S)FTP instead of doing so via the site admin?

Any details regarding your hosting?

PHP Version
MySQL Version
Curl Version
Hosting Provider & general plan (GoDaddy Managed WordPress, SiteGround Shared, custom-managed AWS, etc.)

@mgc That’s rather weird considering I’m on that same hosting setup (@sflwa is too) and using SFTP to fully re-upload the plugin entirely resolved the issue. You might be encountering a totally different issue due to a plugin conflict or something of that sort (I mean, what else would be different between the sites on the same hosting offering where SFTP upload fully fixed the issue for multiple people while it didn’t for you?)

What’s the error you get when you enable WP_DEBUG?

Curious why GoDaddy’s Managed WordPress hosting & SiteGround Shared Hosting experienced and/or is experiencing this issue.

We actually did a live test of this on a Siteground hosted site using the GoGeek plan and there were no issues for us. It’s possible it could be a PHP timeout issue, or it could possibly be something else on the site that is slowing it down. The site we tested on was a pretty light site, so maybe a bigger site with lots of plugins or processes is causing the timeout to occur. Just a thought while we look into this more.

It seems to be an issue with the file on WordPress. I’m having issues even attempting to download it directly from the WordPress page right now. https://downloads.wordpress.org/plugin/google-calendar-events.3.1.32.zip

It doesn’t complete the download. I’ve made this attempt in multiple browsers and other plugins aren’t having a similar issue when I try to download directly…

Appear to be on the virus scan that it hangs. Could there be an issue with the file hash or something on the WP side?

Just to confirm the Zip file has over 13,000 files in it????

• This reply was modified 3 years, 7 months ago by dangarion.