@clwill bummer.
I would say to have a better chance of figuring out the issue provide the following
1) What Theme are you using? And are you using a Child Theme with it?
2) Server environment, Apache? Nginx? Litespeed? PHP version your site is running on?
3) Other plugins you are using (have you tried disabling all the plugins and see if you get Gutenberg back? If it comes back, then turn on your plugins one by one and see which plugin causes Gutenberg to go to a blank screen.
That should be good for starters. If I can’t help, you will have a lot of good info for someone to help.
Thread Starter
clwill
(@clwill)
OK, here goes:
1) It’s a custom theme, really, really basic. Done years ago, based off 2012, I think. As I noted, Gutenberg worked fine until I clicked on “custom fields”.
2) It’s Ubuntu 18.04LTS, running Nginx 1.14.0, using PHP 7.2.10.
3) I’ve deactivated all plugins, same behavior.
And…??
Hi clwill
Well, that is a good start. In my time, and its been a lot of time (lol), I have come to find that old technology and new technology the vast majority of the time will not play nice together. Or if it does only a matter of time before trouble is knocking on your door.
It is sounding like that 6-year-old theme (depends on when it was customized) you have is going to be the culprit.
What I would do (first make a backup of your entire site!) is load up another theme, maybe the new Twenty Nineteen that shipped with 5.0 or Astra, in other words, a theme that is known to play well with Gutenberg and then see if you are having the same issues. If it works well your old theme is going to be the culprit.
If that turns out to be true, to be totally honest not sure it will be worth the time investment to get the old theme “up to speed”. But ultimately it’s your decision.
Good luck to you.
-
This reply was modified 7 years, 6 months ago by
KartHost.
Thread Starter
clwill
(@clwill)
I tried the 2019 theme and it does the same thing.
clwill, have you tried clearing both your web browser cache along with all server cache/website cache after those changes?
Thread Starter
clwill
(@clwill)
I have it working again. With my theme.
What I did was change to 2019, cleared my cache, which got me into Gutenberg, which allowed me to go into options and turn OFF the “custom fields” option.
I then went back to my theme, again cleared my cache, and now Gutenberg works with my theme.
I have no idea what “custom fields” the option page is referring to, my theme doesn’t reference any “custom fields” that I know of, I’m not using any “custom fields” plugins. But whatever it is, it turns on some flag that makes Gutenberg puke.
And no, I’m not going to completely redo a theme that is working fine on two different sites just to make the editor work.
-
This reply was modified 7 years, 6 months ago by
clwill.
Hi clwill, great, glad you got it working, and thanks for the details on what you did to get it working.
Thread Starter
clwill
(@clwill)
Is there some way, some place to report this? Or is this post sufficient?
I’d hate to see this happen to someone else. At the very least there should be some way to do a “reset Gutenberg to defaults” option, no?