Activated Centralized Site Management and now can't access admin

Something interesting – I changed my php in my ipage cpanel from 5.3 to 5.2 and it was working, switching it back and it doesn’t. I went back to 5.2, I disconnected Jetpack while in 5.2 from wordpress.com and reconnected from my dashboard (Jetpack to WordPress.com) then switched the server setting back to php 5.3 and it’s working.

Very odd issues.

Scratch that, must have taken a bit to update, only working with php 5.2. Works fine if I go back to this. Can’t see anything that stands out with php.ini settings for both. Both look the same.

i kinda makes me wonder about the error 500 too. i can only replicate the problem in Php 5.3 on another host. some people are metioning ipage. i suggest try to file your support tickets to them as the highest version of php they have is 5.3 or better yet ask them to have php 5.4 to be available

I checked on 3 different sites running 5.2, 5.3, and 5.4, and I couldn’t reproduce the problem. I don’t have any site with iPage, though, so I won’t be able to test that.

Since that seems to be the common denominator here, I’m afraid all we can do is wait until they give you some more details about the errors by looking at the logs.

sir Jeremy i tried to replicate the problem again on one of my projects on ipage but the thing is… it does not yeild an error on the error logs. the only work around is to activate jetpack on one browserthen re-login on another browser

Got the 500 Internal Server Error immediately after clicking the activate link while using Chrome. Front-end stayed up with no issues. Only admin admin back-end was down.

Chrome ’empty cache + hard reload’ unsuccessful to access admin. Able to open admin in another browser. Cleared Chrome history and then able to access admin.

The ‘Site Management’ is now missing from the module list. Gremlins must have eaten it. Now fearful of that gremlin-infested activate button.

WP 4.1, PhP 5.3, MySql 5.5.32

@jeremy Herve, link to server log sent via jetpack support contact form.

The ‘Site Management’ is now missing from the module list. Gremlins must have eaten it. Now fearful of that gremlin-infested activate button.

Do you see the “JSON API” Module? That’s the one you can configure to activate or deactivate Site Management, as there is no “Site Management” module.

Hey Jeremy, clicked JSON API. There is a ‘deactivate’ button so I guess its live now (or was live from previous 500-error click). From this screen then clicked ‘configure’ and ‘save configuration’. However, unclear on the next step.

@brad If you’ve checked the option available in the JSON API configuration screen, you should be all set, and you should now be able to manage your plugins here:
https://wordpress.com/plugins/

Dude. This is so rocking awesome!

Jeremy, your plugin is going to make site updates so much easier. Thank you for your time and talent in creating this masterpiece.

There is one downside… clearly now see how many sites (some abandoned but not killed) are lacking in their updates. Ugh. I’m off to update’ville.