-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto-save is unreliable #2268
Comments
Since I'm not able to reproduce, could you share a few more pieces of information?
|
Nope. I was watching the page all the time and there was never any message displayed that indicated that the document had saved
I was editing a Page (not a Post). The page was Published and was one that I created an hour or so earlier. I simply added another sentence to a Paragraph block.
I'm using Firefox 54.0.1 (64-bit) on MacOS Sierra v10.12.1 (16B2657) and WordPress 4.8.1 |
@maddisondesigns hi there. I am having a little difficulty in replicating this myself. Would it be possible to show a video and maybe see if you get any console errors? |
Is the page you're editing already published? Published autosave is not yet implemented, tracked at #1773 pending missing REST API requirements. |
Ahhh ok. Yep, the page was already published so I guess that explains it. Thanks. |
In that case, going to close in favor of #1773. Thanks for the detailed report though. |
Issue Overview
I'm finding that the auto-save feature is not reliable. I just added some text to a Paragraph block and waited over 10 minutes (yes, I timed it with a stopwatch), and the page still hadn't auto-saved my changes.
Steps to Reproduce (for bugs)
Add content to a Paragraph block.
Click out of the block and wait to see if page auto-saves
Expected Behavior
I would expect the page to auto-save after adding content to a new block, or at the very least, at a set interval of less than 10 minutes.
Current Behavior
Content not getting auto-saved regularly
Plugin Version 0.7.1
The text was updated successfully, but these errors were encountered: