Can you describe what you see when using the block editor? Are there any error messages or other helpful clues?
Can you paste the raw HTML of the post into pastebin.com, and then add a link to that here? If it’s a bug, that can be useful when reproducing it, which is necessary to fix it.
Thanks for the response, Ian! Here’s a screenshot of the error message that pops up when I try to save the draft. It also periodically pops up by itself when the post tries to autosave. http://puu.sh/Dyz0v/c0a615d8ad.png
When you say you’d like to see the raw HTML from the post, you mean what I’m copying over from the code editor in to the classic editor? Here’s an example: https://pastebin.com/TGvKEh5P
Probably worth mentioning, after I saw your response, I decided to do some quick tests of my own…I noticed that if I make a post entirely composed of text blocks, I have no issue. As soon as I fire a picture into it, it no longer is willing to save. In addition, once I save the post (the one with just text in it), I can’t close it and come back to it with the block editor. It forces me to use the classic editor. Very weird! Again, I ain’t mad, since I can still create a new post with the block editor, make the layout that I need, and then copy the code in to the classic editor. Would be pretty rad to go back to a regular workflow though!
Hmmm, that is odd. Can you try opening the Developer Tools console before you hit save, and then see if there’s anything added to it when you click the save button?
If anything shows up there, can you post a screenshot?
I might not get to it this evening, will give a try tomorrow and report back!
So, the console has shown something, but I have no idea what it’s showing me.
http://puu.sh/DySqL/4946712b8b.png
The first four lines appear as soon as I open a new post with block editor. The rest of ’em all appeared when I tossed a bunch of pictures in to the editor. I did it by copying and pasting code from the classic editor. Funny enough, it didn’t throw those lines out until I switched over to the visual editor.
I’ve found something that may help, but is possibly beyond my capabilities in terms of fixing, since I don’t totally understand what was done here: https://github.com/WordPress/gutenberg/issues/12696
So, I just have to figure out how to edit nginx, basically?
I wonder if you have PHP’s display_errors setting enabled? If there are any errors or warnings shows by plugins (which is very common in lower quality ones), then that will damage the JSON response from the API, and it won’t be readable by the editor.
You can check that by going to the new Tools > Site Health feature in WP 5.2. Under the Critical section, make sure it does not say “Your site is set to display errors…”.
If that does appear, you can follow the instructions to turn it off, and hopefully that’ll fix the problem.
If it doesn’t work, can you click one of the > triangle icons to the left of “unhandled promise rejection”, and take a screenshot of the results?
Also, follow these steps to get some more clues:
1) Open Developer Tools, then the Network tab, then navigate to a post.
2) Type wp-json in the Filter input field, to narrow down the requests.
3) Insert the pictures into the post.
4) Look at the list of requests, and look for any of the new ones where the Status field is not 200. They might be highlighted in red.
5) Click on one of them, then on the Response tab. Copy/paste the text there into a pastebin.
Hmmm, so…my Site Health window doesn’t have a ‘Critical’ section. It does have a list of things though: http://puu.sh/DyXnD/d18491dcea.png
Here’s a closer look at the error in the console: http://puu.sh/DyXuN/cacbff83d1.png
Okay, so there are a bunch of “GET” requests showing 508. Here’s the pastebin of the response: https://pastebin.com/gN4Mt10E
Hmm…maybe it’s my host limiting my site? That seems kind of odd though, since I’m using Cloudflare and AWS. I am dealing with issues of non-stop brute force / hacking attempts though, so it probably has something to do with that.
Ah, yeah, that makes sense. You could probably double-check w/ AWS to confirm. The 508 could be coming from Cloudflare too, but that seems less likely to me since it’s a dynamic asset, and CF doesn’t have rate limits AFAIK.
Hmm, I didn’t even think that it could be AWS limiting things, but I suppose that actually makes some sense. I’ll take a look and see if there’s anything I can tweak there! Thanks for all of your help so far, Ian!
So, as an update: I was using my workaround until noticing that Gutenberg had an update today. Applied update, and now I can update and preview and save posts without any issues. No idea what was changed that fixed my problem, but problem is presumably solved? I’ll bring this post back to life if it somehow rears its ugly head again.
