Blank Admin Bar (all-white) since update

Hello @oakandrocks

Some issues you encounter with your WordPress.com blog or account can be solved by changing your browser settings, refreshing the page, or clearing the browser cache and cookies.

Here is our support doc that explains how to fix these issues: https://en.support.wordpress.com/browser-issues/#clearing-your-browser-cache

Let me know if you have any questions.

My best regards,

Michelle

The issue is present on 2 devices & 4 separate browsers.

Edge
Firefox
Chrome
Chrome Mobile

Hi @oakandrocks

Could you please post your site URL here so that we can have a look?

If you want it to remain private, you can also contact us via this contact form. If you choose to reach out directly, please include a link to this thread.

Thanks!

@bruceallen
oakandrockscom

Hi there

I can’t see any obvious reason for the missing toolbar, but I’m also not sure the issue is related to Jetpack. This post has some suggestions that may help:

https://www.howtosolutions.net/2016/09/wordpress-missing-admin-bar-toolbar/

However, when testing your site, I did notice a general issue with the Jetpack connection. To fix that, would you please delete Jetpack and then reinstall it? You can follow these steps to do that:

https://jetpack.com/support/reconnecting-reinstalling-jetpack/#reinstalling-jetpack

Let us know when that’s done so we can test the connection again.

@drawmyface
Doing so will disconnect my 4 linked accounts.

What will this break?

The bar thing is not that much of a problem and you’re saying this would address a jetpack issue, but i havent noticed any issues with jetpack

Is it a security issue?

@drawmyface Additionally, how did you “test” my Admin Bar? Shouldn’t you need to be logged in for that?

You guys are clearly not going to help me fix my issue.

Closing thread.

Hello @oakandrocks

It’s possible that there might be a conflict with one of your current plugins.

Try disabling all of your plugins except Jetpack, using an incognito browser tab. Then try testing again to see if the issue persists.

If that resolves your issue, you can find what was causing it by enabling each plugin one by one while continuing to test.

Let us know how it goes.