Jack Yan

Hi Jeremy, thank you for getting back to me. I didn’t see your reply till now, but I had deleted Jetpack in the interim.

I’ll give it a go, and report back.

Thanks, Mads, I uploaded it several times and I always do my updates manually. What we wound up doing was downloading a back-up database, saving it on to Mysql on my friend tech’s computer, and essentially redoing WordPress on a new server, and reconnected the data and plug-ins. Seemed to be the only way to do it. I have a feeling this one’s a big lemon. We had to get rid of Jetpack this time as the moment I reactivated it, WSOD came back.

Thank you for coming back to me. So many people don’t when their problem is solved, so I am really grateful.

Yes and no: while I have the basics back, there is no Jetpack, but I will open a thread there and I’m sure Jeremy and the others will be able to shed more light on the reasons for incompatibility with this particular set-up.

An update. Our web expert backed up the database and imported it into a MySql database on his local machine, downloaded WordPress again, hooked it up to the database, ran the update, tested, and uploaded to our web server. So quite substantial surgery over many hours were needed, far beyond the knowledge of most amateurs like me.

When I got in to this installation, all plug-ins were switched off. As I switched them back on, it appears Jetpack is the culprit and simply conflicts with this latest version of WordPress. Neither 3.9.6 nor the latest Jetpack works, with both resulting in WSOD upon activation. Fresh, manually uploaded copies were used.

Hi adsjerreram, did you get yours sorted? I have this same error in my logs. Like you I tried those things and nothing has worked.

Hi Tara, that’s exactly what I had done to begin with, but I have since done it one more time and it’s the same result. I never use the automatic method.

I have a similar error, were you able to get yours fixed?

I managed to find the error logs. Here is a line of someone trying to access the site but finding that it’s all gone:

2016/04/22 08:26:04 [error] 1018#0: *6216037 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 10.181.80.104, server: lucire.com, request: “GET /insider/20110226/fiat-shows-gucci-edition-of-500-jaguar-commemorates-e-type-anniversary-with-ofcial-book/trackback/ HTTP/1.1”, upstream: “fastcgi://127.0.0.1:9000”, host: “lucire.com”

Does this mean anything to anyone?

Also, I think these relate to the site as well and these were happening earlier in the day. It means nothing to me except I know WordPress runs on PHP.

I can’t reach my tech guy, and it’s getting a bit desperate. Any clues would be welcome.

2016/04/22 01:42:33 [error] 1018#0: *6183653 FastCGI sent in stderr: “PHP message: PHP Fatal error: Cannot redeclare get_comments_popup_template() (previously declared in /vol/lucire.com/public_html/insider/wp-includes/template.php:484) in /vol/lucire.com/public_html/insider/wp-includes/deprecated.php on line 3699”, client: 10.239.169.157, server: lucire.com, request: “GET /insider/ HTTP/1.1”, host: “lucire.com”

2016/04/22 01:44:25 [error] 1018#0: *6183871 FastCGI sent in stderr: “PHP message: PHP Fatal error: Call to undefined function _wp_get_current_user() in /vol/lucire.com/public_html/insider/wp-includes/pluggable.php on line 69” while reading response header from upstream, client: 10.181.80.104, server: lucire.com, request: “GET /insider/wp-admin/ HTTP/1.1”, upstream: “fastcgi://127.0.0.1:9000”, host: “lucire.com”

2016/04/22 01:45:01 [error] 1017#0: *6183971 FastCGI sent in stderr: “PHP message: PHP Fatal error: Call to undefined function _wp_get_current_user() in /vol/lucire.com/public_html/insider/wp-includes/pluggable.php on line 69”, client: 10.181.80.104, server: lucire.com, request: “GET /insider/wp-admin/ HTTP/1.1”, host: “lucire.com”

2016/04/22 01:45:08 [error] 1017#0: *6183981 FastCGI sent in stderr: “PHP message: PHP Fatal error: Cannot redeclare get_comments_popup_template() (previously declared in /vol/lucire.com/public_html/insider/wp-includes/template.php:484) in /vol/lucire.com/public_html/insider/wp-includes/deprecated.php on line 3699”, client: 10.181.80.104, server: lucire.com, request: “GET /insider/wp-admin/index.php HTTP/1.1”, host: “lucire.com”, referrer: “https://lucire.com/insider/wp-admin/admin.php?page=stats”

Thanks, Tara, I’ve tried renaming the themes and plugins folders. The upgrade has been done three times so far, each with the same result. I’m awaiting our web guy as he knows more about hosting, error logs and the technical stuff.

Hi Tara, https://lucire.com/insider/

Good news, Jeremy! It was indeed the config for Nginx. Our expert fixed it with this (pasting in case it helps others):

try_files $uri $uri/ /insider/index.php$is_args$args;

He wrote, ‘it tests to see if there are arguments and if there are it adds them transparently into the URL to be processed.’

Jeremy, I think I have stumbled across the answer. We are hosting on Nginx, and I wonder if this is the culprit:

https://jlyman.net/p/related-posts/

This is a bit beyond me but I will get our tech guy behind the server set-up to follow this. I have a feeling this will solve the issue, as we have five WordPress installations and they all seem to have the same problem.

It’s 12.40 a.m. in Australia where he is, but I’ll leave a note for him, then come back to you if this fixes things.

I’ve now disabled W3 Total Cache again, then flushed the cache, but I still can’t get the proper version of that query. ?? I’ve gone to some random pages on the site (there are several thousand posts) but the same thing still happens.

I have my personal blog that has never had W3 Total Cache, and it exhibits the same behaviour for some strange reason. I’m happy to provide the URL here if you feel it could be useful. The blog has some different plug-ins but I have gone through the same exercise of disabling and enabling.

Thank you so much for keeping on this, Jeremy, it was indeed checked. I’ve now unchecked it and flushed a few times, but still no joy. ?? I have double-checked that anything that says ‘minify’ in the W3 Total Cache settings is switched off.

Hi Jeremy, I followed your advice and began disabling each plug-in. None made a difference, and I couldn’t get a window exactly the same as yours for the console (I use Cyberfox, a 64-bit version of Firefox). However, I began tackling the Javascript errors you had in your very helpful screen shot (thank you, it was a massive help) and some were down to the skin, thanks to old code provided to us by various parties. I’ve replaced a lot of them; there’s only one I await a replacement for, but the rest seems to be gone based on the console in Cyberfox.

I wonder if these remaining Javascript errors could be the culprit.

I’m not the most computer-literate guy in the world but hopefully this is the right direction.