Support » Plugin: Gutenberg » Saving, Updating fail error message in Gutenberg 3.6.0

  • Resolved Doug Nix

    (@macadk)


    I have Gutenberg 3.6.0 installed on my site and have now created a couple of posts using the new editor. When I go to save a draft post or update a published post, I get an error message saying the save/update failed. If I navigate away from the post editing page and come back, the changes were in fact saved. I’ve used the Chrome Developer Tools console to see if there are any errors coming up, and none are showing.

    On the off chance that there is something wrong in my htaccess file, I re-saved my permalinks to restore the htaccess file. No change in the behaviour of the editor was noticed.

    Any thoughts on how to fix this would be appreciated.

    The page I need help with: [log in to see the link]

Viewing 12 replies - 1 through 12 (of 12 total)
  • Corey McKrill

    (@coreymckrill)

    Hi @macadk,

    Looking at the changelog, it appears that this issue might have been fixed in 3.6.1. Have you tried updating yet?

    Unfortunately yes. I am currently running V3.6.2 of the plugin, and I still have this issue.

    Corey McKrill

    (@coreymckrill)

    Hmm. It looks like there are a couple of similar open reports in the GitHub repo:

    https://github.com/WordPress/gutenberg/issues/8241
    https://github.com/WordPress/gutenberg/issues/9146

    From those tickets, it sounds like some people are having issues if they’re using CloudFlare or they have security plugins installed. Do either of those situations apply to you?

    No. I looked at those posts some time ago when I first tried the Gutenberg editor, and neither applied. I discovered a problem with Easy Short Codes plugin, so I deleted that and it fixed the problem for a while, but now it’s back.

    Corey McKrill

    (@coreymckrill)

    Hmm, ok, maybe you’ve found a new bug. Bear with me, I have another idea to try and get more information about the error.

    I’ve used the Chrome Developer Tools console to see if there are any errors coming up, and none are showing.

    Instead of the console, let’s try looking in the Network tab. If you have that open while trying to save, you should see an entry in the Network tab with a name, something like /wp/v2/posts/12345, it should be in red, showing that there was an error. Click on that entry, then Headers. What does it show?

    Hi Corey,

    So I did as you suggested, and I can see no errors popping up in the network tab. I can send you a copy of the network log if you’d like to have a look. I was able to replicate the error twice on one post I was editing which was completely created in Gutenberg.
    Let me know if you want the network log, and how best to send it to you.

    Hi Corey,

    I can provide screenshots of the error and the status in the Developer Tools if that would be helpful.

    I think the error message is bogus, but I can’t lend much more light on that topic.

    Corey,

    I left the post open overnight, with the network log stopped but the console open. This morning I am seeing a pile of errors in the console that were not showing yesterday. Here are some samples.

    Failed to load resource: the server responded with a status of 400 (Bad Request)
    /wp-admin/admin-ajax.php?doing_wp_cron=1534894281.5693430900573730468750:1

    Failed to load resource: the server responded with a status of 400 (Bad Request)
    /wp-admin/admin-ajax.php?doing_wp_cron=1534894702.5551021099090576171875:1

    Failed to load resource: the server responded with a status of 400 (Bad Request)

    36 autosaves:1 Failed to load resource: the server responded with a status of 403 (Forbidden)

    2 admin-ajax.php:1 Failed to load resource: the server responded with a status of 404 (Not Found)

    Corey McKrill

    (@coreymckrill)

    Ugh, how frustrating that the error message is so inscrutable and there aren’t more details available. I’ve seen those “Failed to load resource” messages in the console before as well, and I agree that they most likely are not related.

    Without any better information available, I guess we can fall back on the plugin deactivation method. You’ve already disabled Easy Shortcodes, but have you tried disabling everything else (besides Gutenberg) to see if that changes anything?

    Hey Corey,

    No, I haven’t, but I will try that next. The new troubleshooting mode should be very helpful for this… 🙂

    Hey Doug and Corey,

    I am facing a quite simular problem, if not even the same.
    I get the “Updating Failed” message on autosave and manual Update. ( But WordPress actually saves what i’ve done)
    My console’s error section is filled with React error-messages but nothing that effects the mentioned Error Message that shows up in Gutenberg … i guess.

    I deactivated all Plugins. There is no error in the Network tab or the console ( besides the React ones).

    The only thing that makes a difference to me is the shortcodes I use in the Gutenberg Page.( The shortcodes include scripts)
    Some shortcodes throw the error and some do not. At some point i thought this would be caused by BOM -> so i removed it on my script files, what seemed to work, because the error disappered.
    Unluckily it does not work …

    Have you found any solution i can try ?

    Moderator Marius L. J.

    (@clorith)

    @mariushammer This topic is many months old at this point, and related to a version of Gutenberg that’s been obsolete for just as long (we are on Gutenberg version 4.1.1 right now).

    If you are experiencing issues, I would encourage you to create your own topic at this time. To avoid unnecessary noise for the old topic participants, I’m going to close this thread.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Saving, Updating fail error message in Gutenberg 3.6.0’ is closed to new replies.