Updating failed on autosave

Hi there.
That’s awful… With the new version of Gutenberg 4.5 did this resolve?
Are you able to see what error message is in the Browser Console?
In Chrome: 3-dot menu top right > Tools > Developer > Browser Console.
You can leave it open while working on your post and the moment the “Updating failed” message appears there should also happen an error message in the browser console.

Hello Birgit,

I’m still getting the ‘Updating failed’ message on auto save after upgrading to Gutenberg 4.5.1. However, it only seems to be happening on one particular page. I’ve checked the Javascript console (Firefox) and found nothing being reported there.

If I close the ‘Updating failed’ message, then click the Update button, I get another ‘Update failed’ message as soon as saving completes. Despite the message, the update does save any changes I make.

I will start removing elements from the page to see if I can determine why this particular page is producing this issue.

Great, that you were able to narrow it down some more!

Are you using any 3rd party blocks on this particular page?
Or a blocks that uses outside services?

Hi Birgit,

I’ve done some testing and tracked the issue to a shortcode ‘google-map-v3’ from the plugin Slick Google Map. This plugin hasn’t been updated for about 3 years and it seems the author is not actively supporting the plugin. The plugin has caused another problem with Gutenberg with the page ‘Parent’ setting not showing. I reported that previously. This issue doesn’t seem to be a problem any longer. Since the last two updates to Gutenberg, the parent setting seems to be working.

I don’t understand why the shortcode should cause this problem with Gutenberg. Isn’t it just a piece of text enclosed by []? If I change the shortcode name to ‘google-map-v’ there is no problem, but of course the shortcode won’t work on the front end.

What is Gutenberg doing with shortcodes?