Immediate crash of editor upon opening new post page (solved by updating nginx config) #12655
Comments
|
Hi @Kilian, Thanks for the report! I'm unable to reproduce this in WordPress 5.0. A couple follow-up questions:
|
danielbachhuber
added
the
[Status] Needs More Info
|
Got 2 reports from our customers on that as well, unfortunately :( Trying to debug remotely but it's individual customer's computers. Mostly Chrome. Will try to provide more details soon |
|
Hi, I also have this problem. |
|
@danielbachhuber I run many plugins, but none that should change the edit view too much. I'll try regardless. In the mean time. Worthy of note is that my Wordpress database has been with me since 2006, so it has had a fair number of migrations. Additionally, the error in devtools provides slightly more context compared to the 'copy error' text: Furthermore i get a 403 on Edit: On chrome 71, the editor crashes still but the actual error is different: |
|
Thanks for the additional data, @Kilian.
This is helpful. It seems like there are some additional recent reports in #9556 (comment) Also, #8802 is an earlier report. The immediate problem is that Gutenberg is trying to access data about taxonomies, but the Can you take a look at your "Network" tab in your browser's Developer Tools to see if any API requests are failed? And, if so, share screenshots of those?
This is a Jetpack issue and likely unrelated (but you never know). |
|
Other than the 403 mentioned there are no other failed requests. |
|
I noticed that #8899 (comment) mentions the |
designsimply
added
the
[Type] Help Request
|
I'm seeing the same errors as @Kilian in Chrome. Disabling my plugins did not solve the problem for me. |
|
I have the same problem. With posts only. Pages work fine. I run Nginx v1.14.0 with PHP-FPM v7.2.11 All plugins are disabled, permalinks re-saved. Update: The problem is gone when permalinks are set to "Plain", but persists when permalinks are set to "Post name". No relevant message in Nginx error log (debug level). Here is something from access log: Firefox Developer Edition Console: |
|
Same error here, too. Wordpress 5.0 upgrade completed a day or two ago (I came here from another issue referencing this one). Plugins all disabled but exact same error i.e. momentary display of the editor that's then replaced by the error reported here. Disabling Gutenberg removes the problem. |
|
same error, if you are trying to create a new block from manage all reusable blocks wp-admin/post-new.php?post_type=wp_block |
|
Fixed tldr: if you run Nginx, you might need to update your nginx config.
This made me check. The editor works fine for pages, it's just the posts that crash.
I indeed have a custom permalink structure: After adding this to the end of /index.php, the editor now works for posts too! |
|
Thanks for the update, @Kilian. The specific issue you found make sense to me. If your Nginx configuration was incorrect, then It was only a problem with Posts for you because you don't have any taxonomies assigned to Pages. |
|
Unfortunately, my issue is different so I'll log a new bug |
|
I can confirm the issue, same browser version and OS. |
|
Exact same issue here. Still remains with WP 5.0.2. FreeBSD 11.1 |
designsimply
changed the title
|
@AlirezaSedghi the error in your case is a little different. Can you please report your case at #12982 and include your WordPress, OS, and browser versions? @mdparker @igortitarenko @digitalformula if you haven't already, please try the solution posted at #12655 (comment) if you are using nginx. @umakantsharmacedcoss issues with @stz184 @micele I would like to close this issue since it's getting very long and because one solution that is working for some was posted so it's possible your issue may be different. Would you mind please opening a new issue with the details of your case including: the error you see on screen, the error you see in your browser console, WordPress version, OS & browser version, note whether you've tested with all plugins deactivated, and your the location rule from your nginx config (or the corresponding rule in Apache if you are using Apache)? |
|
@designsimply No nginx here. It's Apache 2.4.17 on FreeBSD. |
|
@designsimply
Ignore the above, sorry. I found my server was configured in a way that pointed me to the wrong site conf file. After finding I was editing the wrong conf file and then making the changes in the correct one, everything seems to working. Thanks for following up on this! |
Thanks! It's fairly simple to assume its a URL re-write issue when changing the default behavior in WordPress can resolve this issue. For those on Apache, you will need a similar mod. Perhaps the codex needs updating to include this? Link |
Avoid hitting WordPress/gutenberg#12655
Describe the bug
Upon opening the "new post" page, the editor is briefly visible before being replaced by a "The editor has encountered an unexpected error." popup. There is a button "attempt recovery", which does not work.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
not see error.
Screenshots
Desktop (please complete the following information):
Additional context
The Gutenberg editor in wordpress 5.0. I cleared my localStorage settings but the error remains.
** Copies error **
The text was updated successfully, but these errors were encountered: