-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gutenberg not showing draft posts (solved by clearing browser cache) #9095
Comments
Uninstalling the Gutenberg plugin will not affect post content, and you should be able to edit Gutenberg content with the classic editor if you cannot use Gutenberg. Could you post screenshots and–if possible–the content of your post that won't open? It also could be handy if you could check your browser's error console to see what error Gutenberg is encountering. What web browser/operating system are you using? |
I cleared my cache and the problem was fixed. |
Great! I’ll close this issue as I wasn’t able to reproduce it. Was it your browser cache or a WordPress cache you cleared? |
It was my browser cache.
…On Mon, Aug 20, 2018 at 5:37 AM, Matthew Riley MacPherson < ***@***.***> wrote:
Great! I’ll close this issue as I wasn’t able to reproduce it.
Was it your browser cache or a WordPress cache you cleared?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#9095 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AogZ9L6foHAZTZYND4TTdHQMh3dqq8bkks5uSoNbgaJpZM4WBwnp>
.
|
I've had the Gutenberg plug in installed for about a week, and have done okay with it. Small issues like with creating hyperlinks and not being able to customize their appearance. After writing a 2000+ word draft yesterday, I wake up this morning and all my post drafts won't show up. I click into them and it's just showing me a blank white screen. I can't click or type or anything. I'm afraid to uninstall the plug in and end up losing all my work.
Please advise.
The text was updated successfully, but these errors were encountered: