I’m sorry to hear you’ve run into issues. Jetpack is compatible with WordPress 4.1, but obviously something went wrong on your sites.
Could you give me more details about the problem? By “lose everything”, do you mean that you lost your old Jetpack settings, some of your Jetpack data like your stats, or some of your sites’ content?
When updating it corrupts the file everything is in.
The file has to be deleted and re-added, we also had to re-add the domain.
I get an internal server error 500 after installing the updated version of jetpack.
I have updated two sites and this has happened to both.
I will not be updating any other sites with jet pack at this time because of this problem .
I get an internal server error 500 after installing the updated version of jetpack.
Could you check your server error logs around the time when you got the 500 error? The error details should tell us more about what’s causing the problem on your sites.
If you don’t know how to access your server errors logs, your hosting provider should be able to help.
Thanks!
I have the same issue, and I’ve seen TONS of posts all saying they’re getting a 500 error after enabling “Central Site Management”, yet I see no answers posted. Is that because (and I’m writing to Jeremy here, the Happiness Engineer) no one has followed your instructions and posted the error logs? I’ll be glad to do so — what am I looking for once I find the logs? They will no doubt be big.
@afwings There were indeed a few people reporting 500 errors, but I haven’t been able to reproduce in any of my test sites, and no one has replied to me with the error logs yet.
If you have access to your logs, I’d suggest looking for all errors around the time when you’ve updated Jetpack. You can also send me the logs for the whole day, and I’ll look through them.
Thanks!
Thanks. I did get my error logs, and although there are a good many of them labeled fatal, none of them relates to Jetpack. That’s strange though, because this has happened twice to me, the next thing that happens after I click the button to activate Single Sign On, the Admin control panel goes away, and is replaced by the 500 error. If it’s not Jetpack causing that, it’s awfully coincidental.
Here’s the typical fatal reference in my logs:
PHP Fatal error: Call to undefined function related_posts() in /hermes/waloraweb060/b2804/moo.<domain_name_here>/blog/wp-content/themes/orange-subway-10/index.php on line 22
Since it was a new installation, I just deleted it and started over — and learned not to use Single Sign In.
after I click the button to activate Single Sign On, the Admin control panel goes away, and is replaced by the 500 error.
It’s weird that you get a 500 error, but it doesn’t appear in your logs.
Could you try to enable WP_DEBUG_LOG, as explained here, and let m,e know if you get any errors in wp-content/debug.log?
I did that, but nothing exciting to report. I created a new blog strictly for the purpose of testing, and used that one for this debug test. I added
define( WP_DEBUG_LOG, true );
as the first line of code (beneath the <?php line), and never got the debug.log in the wp-content folder. I was able to activate single sign-on without error.
Ok, I got it to crash. My mistake earlier, it’s “Centralized Site Management” that causes it to crash. I still don’t have a debug.log in wp-content though.
Checking my Control Panel CGI logs, there are no fatals, and 3 warnings pertaining to this blog:
20150126T082108: www.fbgcofc.com/testing/wp-cron.php
PHP Warning: Invalid argument supplied for foreach() in /hermes/waloraweb060/b2804/moo.fbgcofc/testing/wp-content/plugins/mojo-marketplace-wp-plugin/inc/user-experience-tracking.php on line 276
PHP Warning: Invalid argument supplied for foreach() in /hermes/waloraweb060/b2804/moo.fbgcofc/testing/wp-content/plugins/mojo-marketplace-wp-plugin/inc/user-experience-tracking.php on line 294
20150126T093517: www.fbgcofc.com/testing/wp-cron.php
PHP Warning: Invalid argument supplied for foreach() in /hermes/waloraweb060/b2804/moo.fbgcofc/testing/wp-content/plugins/mojo-marketplace-wp-plugin/inc/user-experience-tracking.php on line 294
This is a site hosted at FatCow, which I believe to be an awesome host, but every WP installation includes the Mojo Marketplace plug-in, which does seem to log a good many CGI errors. Not sure how this can be the cause of the crash when I try to implement the Centralized Site Management, but it’s all I’ve got.
What happens when you deactivate the Mojo Marketplace plug-in? Does your site still crash when you try to activate Centralized Site Management?
It’s crazy. I created a video so you can see (I paused the recording during the time I was connecting Jetpack to my WP.com account). Video’s 2:22, with no sound.
http://screencast.com/t/GfVNC9fUby1
That’s interesting. I assume the 2 last errors happened before you actually deleted the MOJO plugin.
I don’t understand why that 500 error wouldn’t be logged anywhere in your error logs, though. Could you ask FatCow about this? Can they look into it and see if they can start logging that error somehow?
I have filed a support ticket with them. I’ll let you know the result.
