@ike It’s a work computer and I’m not able to update to the absolute latest versions of browsers. It has to go through IT’s labyrinthine testing and approval process.

I deactivated all the SP plugins after disabling WP stats. Once WP stats were turned back on I had the same problems accessing the SP admin pages. I’m on a Mac now, Chrome v41.

I was just relaying a post that Steve didn’t manage to add at the time. While it’s probably best to continue the discussion with Steve or Andy who know far more about this stuff than me – I would imagine it might unfortunately come down to not running the latest versions. I think they are pretty busy currently but I’m sure they will pick up when they can.

@gorky5 when you try to use a menu, what is reported in the browser console?  any js errors?

struggling since I cannot replicate this on three sites now…

Mr. Papa and Yellow Swordfish, sorry i got busy and forgot to give you a list of my plugins.

Here is an mp4 screen video with some new information. The blank white screen has been this way for a long time. My plugins list is in the video. Might have to refresh your browser to view this video.

Thanks for all you guys help!

Regards, Ed.

is this jetpack or jetpack light?  3rd user has reported it but mentioned something about jetpack light which I have never heard of…

and what happens if you turn off all the jetpack modules?  still problem?  and then turn them on one by one and see if we can isolate which one conflicts…

We need to try to get jetpack working locally (vice on live sites) and see if we can replicate… on live sites, have not been able to make it happen…

From what i see JetPack Light is another plugin that disabled all but a few options, and JetPack is still required. If anyone is using it I’d disable / delete it. The current JP allows individual module disabling.

Steve Andy, if you guys want to poke around in my blog send me a pm for the login credentials.

Regards, Ed

dang… just loaded up jetpack locally on test site and works fine with SP…  now being localhost, some modules are auto disabled… so could still be specific jetpack module conflict…

@fidosysop-2 are you able to deactivate all jetpack modules and see if working?

I will try disabling all I have activated in the morning. Using stats, widget visibility, and shortlinks. I’m wondering if my theme could be causing it?

Ed “DOC” Koon blog.docsplace.org fidosysop@gmail.com Internet Webmaster Help On Apr 6, 2015 8:25 PM, “Simple:Press Support” wrote:

>

I thought you had already tried the wp default theme?  if not, after the module test, would be good next test…

thanks!

Just thought I’d chime is here since I experienced the similar issues of SP Admin sub-panels not loading. All top level SP admin pages loaded fine from their links in the sidebar. But attempting to load the Ajaxy sub panels only resulted in jumping to the top of the page as described by the original poster, @fidosysop I believe.

For the record, I use the Jetpack Lite plugin which strips out all the bloatware from Jethack to only provide Stats and Shortlinks. After de-activating both plugins, the issue went away and I was able to access all SP Admin panels.

But then this morning, after re-activating both, the SP Admin is still functioning as expected.

Only other variables for me include:

Issue first arose immediately after upgrading to SP 555 and uploading the Reboot theme and a tweaked child theme, which I had working fine on our dev install.

Ours is a multisite network, with SP running on the main site only.

I did run the Reset combined CSS/JS  comand during my troubleshooting, after uploading the new themes. And I did remove legacy mobile & tablet theme data from our wp_1_sfoptions table as Andy suggested.

I had also deactivated and reactivated all SP plugins during my troubleshooting, and re-uploaded a clean simple-press install folder.

Who knows which if any of these steps fixed the problem. I do know Jetpack is always communicating with their servers so it may have been a temporary network issue. And I was on a satellite connection at the time, which tends to have some serious latency…

Just rambling and reaching for straws at this point, in hopes that something may help y’all…

Good luck!

The sequence that plugins are activated can make a difference to stability because WP tends to load plugin scripts in the same order in which they were activated. Is it possible that by doing whatever you have done this sequence may have been reversed?

Yellow Swordfish said
Is it possible that by doing whatever you have done this sequence may have been reversed?

If that question is for me, anything is possible! The past few days have been pretty crazy as I’ve finally completed out site overhaul.

That could make sense though, Since Jetpack Lite does require Jetpack to be activated…nowhere in either docs/faqs are there instructions about which must be activated first, if that is the case.

Did some further troubleshooting on this…

Yes, my SP admin panels all loaded fine after activating both Jetpack and Jetpack lite.

But then ya got me thinking…

I visited the Jetpack settings, connected to my wp.com account, and actually activated the two components, Stats and Shortlinks. Guess What? The /spa-themes.php# link bounce me to the top again…

Deactivated Stats component (still connected and shortlinks component still active.) And, SP Admin sub-panels load as expected. So…

Revisited JP Modules: Deactivated Shortlinks and Reactivated Stats, reloaded top level Themes panel… And, non of SP Admin sub-panels load, clinking link only jumps page to top.

Deactivated both Shortlinks and Stats, reloaded top level SP Admin, And… all subpanels load.

Activate JP Shortlinks module only…  subpanels load.

Activate JP Stats module again… and, you guessed it—all # links to subpanels fail.

I think we just identified the root of the problem. At least the problem I encountered! As for the cause, well… I’ll blame it on the gremlins and leave a fix, if any, up to those who understand what’s happening and why much better than I.

Now, as long I can remember all this, the next time I experience the issue, I’ll know what to do for a workaround.

Hope this helps somebody!

problem is jetpack stats and forum admin works fine on the four sites I have tested it…  but is consistent with the OP here…  just not sure where to go from here…

I disabled my JetPack modules one at a time with the exception of stats. Disabling stats did allow sp admin access. I’m afraid to use another theme. Last time i disabled DaisyChain Pro i lost all my css formatting and had to restore from that mornings db backup.

It’s the stats module that’s being the PITA! At least in my situation on two blogs.

Thanks again for all you guys help.

Ed