Jetpack Dashboard and Settings pages are blank

Hello Ken,

Thanks for reporting this! I tried to replicate the issue, and while doing that I found out that you’re running an old version of PHP.

Could you try updating it to its latest version and see if that gets things better? Your hosting provider should be able to update the PHP version for you, otherwise we have put together some instructions here:

https://docs.woocommerce.com/document/how-to-update-your-php-version/

You may also want to increase the memory available to WordPress:

https://docs.woocommerce.com/document/increasing-the-wordpress-memory-limit/

If that doesn’t work, can you check your error logs to see what exactly is going wrong? Your host can help you find them if you need help, and you can send them over to us directly via this contact form. (You’re welcome to mention this forum thread as well)

Let me know what you turn up!

Thank you! That gives me a place to start. I’ll let you know what I find out.
What’s the lowest recommended/tested PHP version for Jetpack?

Ken

• This reply was modified 6 years, 11 months ago by ken524.

Stefania,

I sent you more info via the form on the Jetpack support page.
————————–
If any others have a similar problem and are following along, short story is that all Jetpack updates after 4.7.1. display blank Dashboard and Settings page on my WordPress site. Tested all by deleting and installing via SFTP. I also deactivated all plugins to rule out interference. The pages load down until the end of the [link rel=’stylesheet’] tags (not very far).

Ken

• This reply was modified 6 years, 11 months ago by ken524.

Holy Cow, I fixed it.

My site is on GoDaddy’s Managed WordPress which includes a staging site.

I cloned my site to the staging site, then went to the Plugin page and updated Jetpack to the most current. It immediately started working.

I noticed that Jetpack didn’t automatically go into Safe Mode like it usually does in the Staging environment. It thought it was the real site and took ownership of all my stats and subscribers.

I pushed staging back to production. When I logged back into production I got a warning that Jetpack thought it was in a staging environment and went into Safe Mode. But it was working ?? . I clicked the Safe Mode link that asked if this was a new site that needed the Jetpack stats to migrate from the cloning site. Done. Everything working.

If a Happiness Engineer can explain to me what the heck happened, that would be great. If not, at least things are working again as they should.

Whew!
Ken

• This reply was modified 6 years, 11 months ago by ken524.

Hey @ken524, I’m glad to hear you eventually fixed the issue!
It was an identity crisis problem:

https://jetpack.com/support/safe-mode/#what-is-an-identity-crisis

To avoid that happening again in the future, you could set up staging mode on the staging site to make sure that site never comes polluting the data of the production site. This should make the trick ??

Please let me know if you have any further questions or doubts!

Hi, @erania-pinnera,

I’m familiar with the ID crisis issue. That was an easy fix. The reason I had the ID crisis was due to Jetpack not working properly. The act of moving my site to staging somehow resolved the original problem (see thread title).

All is well now. Happy holidays!
Ken