jsrudderham

I’ve just begun migrating to a new server (running PHP 7) and, having just moved my WordPress blog to that server, I can confirm that JetPack now works as it should without turning the site white.

However, I did run into another issue/problem. After activating the JetPack defaults, none of my images were showing.

One of the “default” settings is described as “Speed up images and photos” and this uses a service called “Photon” which appears to use a CDN to serve your images from wp1.com. I only realised this on investigating why none of my images showed up.

It appears that because I have hotlink protection enabled, “Photon” couldn’t grab my images to “speed” them up, so they didn’t display at all.

As soon as I turned off “speed up images and photos”, my images were served up from my own site as they were before and everything displays properly.

Just another one to beware of.

Interestingly, that article linked to by @sandyjuettner242 also states “…more than half of all WordPress sites (55.6%) are using unsupported versions of PHP (versions 5.2 – 5.5).”

Does that mean more than half of WordPress sites (which are presumably using JetPack) have also run into the “white screen of death” issue? That must be a lot of upset people who are, presumably, all deactivating JetPack as we speak.

You link to a page and say that “minimum required PHP version as advised by WordPress” is version 7.0, but that isn’t what the page says. It says the recommended version is version 7, not the required version as you say. You also miss the bit that says “WordPress also works with PHP 5.2.4+”.

I believe I’m running php 5.3.29 which, I appreciate, is outdated but it’s not simply a case of “upgrading to version 7”, as that is likely to affect other sites on the server. Our procedure for upgrading is to migrate sites one-by-one to a secondary server which has everything updated/upgraded, checking for issues, before moving on to the next site. This process is due to begin over the coming weeks and is not something that can be rushed due to a glitch in a Jetpack update.

At present, the only available solution is to disable Jetpack. Thanks for investigating the issue.

I had the same issue.

Logged into my dashboard, saw that there was a JetPack update available, so I updated it as I normally do. Then my blog wouldn’t display any pages – whitescreen only.

Fortunately, I’d only updated JetPack. As soon as I disable it, my blog comes back.

From what I’ve read, it’s probably something to do with PHP version (although everything I’ve read says that applies to JetPack 4.8, not the 5.1 that it’s updated to). I know I’m running an old version of PHP, and I’m due to be switching servers in the not-too-distant future – which is when I’ll bring PHP bang up-to-date), but to have an update available with no warning that it could cripple a site running a particular version of PHP was a bit scary.

So, I guess, for the time being I’ll be running my blog with JetPack deactivated.