Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Permanent crash / not recoverable (solved by updating the permalink structure) #8899
Describe the bug
Desktop (please complete the following information):
See also: #3953 (comment) someone left a new comment 12 days ago from the time of this new report (Chrome & Firefox, no SEO plugins).
Here's the error copy without any plugins attaching itself to the editors (gutenberg and classic).
I tested with Firefox 61 on Windows 7 and was unable to reproduce the problem using WordPress 4.9.8 and Gutenberg 3.5.0 (20s). Noting that I tested with a stable release and you appear to be testing the development version and so I should loop back around to try testing that as well.
May I ask what plugins were still active at the time you did your second test? May I also ask what theme you are using (may not be relevant, asking just in case).
I see the same error with a basically fresh install (Firefox 60/Linux Mint Cinnamon, WP 4.9.8, no other plugins, default theme Twenty Seventeen, only update was from Gutenberg 3.4 to 3.5/production versions; the crash happens for both), for both tags and categories. No terms have been entered, so basically there is only the "Uncategorized" category.
I then both entered a category and a tag to see if this was caused by empty lists, but it made no difference.
The ability to use Gutenberg can be restored by deleting the
Log output with
A crash also happens with Chrome 68, but with a slightly different stack trace (React error report is identical):
I found a similar report at #8456 and the source of the problem in that case was Cloudflare and if that is the cause for your trouble as well then updating to the latest version should resolve the problem.
There is also a note in #8456 about permalink structure (ref) and a note in #8802 about rewrite rules being the cause of the same error (ref). If you aren't already using the default permalink structure, can you try that to see if it makes the problem go away? Are you using any custom rewrite rules on your server?
OK, here it is:
After a fresh install, option
The source of the problem is in the installation call to
So, for my case (neither mod_rewrite nor nginx), the second structure is supposed to be used, but it isn't. While I understand WP Core has no reason to accomodate every existing server setup, maybe it is worth finding out why the test routine fails for lighttpd.
Not to mention that it is a bit strange that this trickles down to Gutenberg.
referenced this issue
Aug 16, 2018
I got the same crash again and to recover, as per what was suggested above, I can get Gutenberg back after clearing Local Storage.
It appears that, on my end, it has to do with opening the Categories and Tags section (for Tags, it crashes for existing posts with Tags already defined; but for new posts, it crashes when clicking the Tags field).
I don't have the issues experienced in the linked reports like stuck "saving draft" and not generating previews -- I had these two last week of July and first week of August only. Also, I'm on free Cloudflare so WAF is locked to Off and the Firewall Evets log for it is also empty.
I turned-off Cloudflare to test but still crashing. I checked the server for any related rules mentioned in the other reports but I don't have those either.
In addition to that, I never encountered the crashes until this August or after the recent minor update by Wordpress, the one where they encouraged installing the Classic plugin. (Yet, even without the classic plugin, it crashes.)
The workaround I have is to just avoid opening the Categories and Tags sections and then edit in Classic. No other areas of Gutenberg is causing the crash, only Categories and Tags, which wasn't the case before August.
I am going to close this as it appears a solution was posted.
@techmagus, if you are still having trouble can you let me know? If things are still problematic for you then I would like to help track down a better solution that what has been discussed above.