Hello,
I am having an issue with AutoSave on several of my sites that use Page Builder. After a random amount of time, AutoSave will kick in and start saving, disabling the Save Draft/Update/Publish buttons, but the buttons are never re-enabled. A workaround is to use Inspect Element (in Firefox or Chrome) to remove the CSS “disabled” class from the buttons so I can hit save, but this is 1. a pain in the ass and 2. sometimes doesn’t work.
I’ve tried disabling all plugins and using a default theme but the issue doesn’t go away and remains even when Page Builder and a Twenty-X theme are the only active plugins.
Here is a screenshot of this happening.
I will get a constant https://*website*/wp-admin/admin-ajax.php 404 not found and be unable to update. This does not happen if I don’t have Page Builder activated.
Any assistance is appreciated.
Hi, thanks for the detailed report. I haven’t ever seen this come up with Page Builder so I’m working this for the first time.
I realize this topic is for Gutenberg but I wonder if some of the points are relevant: https://github.com/WordPress/gutenberg/issues/9220.
Any chance you’re using Bluehost? Is your internet connection reliable? Any particular task being carried out when this happens or random?
As an alternative to troubleshooting, if time is in short supply, it looks like auto-save can be disabled: http://billauer.co.il/blog/2017/01/disable-autosave-wordpress/.
Thank you for your reply.
Firstly, I am not using Bluehost and have a reliable connection. Generally it happens after editing a SiteOrigin block/widget, although I’m only using a handful – Hero, Editor, Image, Headline and the Custom HTML default widget.
I’ll try your suggestions, but I previously tried making Autosave run less frequently (once an hour) but the perma-autosave bug still happens after about 10-20 minutes.
Thanks for your feedback. The issue on GitHub is still open. Given that you’re also working in the Block Editor, my guess is that it’s the same challenge. I’ve subscribed to the issue. Perhaps you can test once it has been resolved?
I’ve not noticed any changes, I’m still seeing the bug in the few hours of testing.
Out of curiosity I’ve also tried installing Classic Editor, but the bug still crops up.
Super annoying for sure. The bug report is still open on GitHub meaning it hasn’t been attended to yet. I’ll chat with the team this evening but I imagine it’s the same issue described by various users in that issue report on GitHub.
To confirm, after installing the Classic Editor, this issue arose while working with Page Builder in its classic form using widgets in the classic interface?
Yes, I’m using the SiteOrigin Page Builder on my posts and pages and getting the infinite autosave bug, whether I use Classic Editor to disable the new Guternburg 5.0 editor or not.
Thanks for clearing that up. Let’s focus on admin-adjax.php going 404. Please, could you try reaching out to your web hosts and ask them to check their ModSecurity logs to see if admin-ajax.php is perhaps being blocked?
Here is a screenshot of what happens when admin-ajax gets a 404:
https://cdn.discordapp.com/attachments/372729346151940097/575289810890260480/admin_ajax_404_not_found.png
As far as I am aware, admin-ajax.php isn’t being blocked (otherwise I would have this bug happen instantly) but I’ll contact my hosts and ask them.
My hosts got back to me and they said that admin-ajax.php wasn’t blocked, but they are looking into it further.
Thanks for the update. With regards to seeing this issue immediately, what we’ve seen is the past is admin-ajax being blocked after too many requests so it isn’t something that presents immediately. Hopefully, your hosts can spot the issue, let us know what they say. Thanks.
Hello,
No update from our hosts yet, but delaying autosave to only happen every hour hasn’t helped matters. Autosave still kicks in and stops finishing with the same 404 on admin-ajax.php. I’m going to try disabling autosave and see what happens.
Thanks for the update. Hopefully, that helps. Let me know.
Hello,
Between increasing the times between autosaves and the increasing of PHP resource limits further by my website hosts, the issue seems to be rectified.
Thank you for the help, you have been insanely helpful in trying to sort out the problem.
That’s great news, really glad to hear you were able to find a setup that prevents this from happening. It’s the last thing you need when you’re trying to get work done. Thanks for the update and support :)
Cheers for now.