You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
when a session times-out/expires or crashes during editing a draft entity and the page is reloaded, the user is presented with a browser confirmation asking if they wish to reload the local backup version - "A local backup was recovered for this entry, would you like to use it?"
When selecting Yes the edit page briefly loads the unsaved backup version before automatically reloading the page again. Upon the reload, the restored version is replaced with the last saved version content.
The workaround right now is to quickly select content and copy to the clipboard before the page reloads.
To Reproduce
Steps to reproduce the behavior.
Using editorial workflow, edit an existing saved (unpublished or published) post
Create changes to the content of the page, do not click save
Copy the full URL from the browser address bar and paste into a new tab of the same browser
When presented with backup recovery prompt select Yes
Confirm restored content appears in edit page
Wait approximately 5 seconds before page reloads - confirm that non-saved restored content is now missing/reverted
Expected behavior
When selecting to restore un-saved changes, the page should load the locally backed-up version and persist these changes until the user either clicks save or discards the changes by choosing to leave the page intentionally
Describe the bug
when a session times-out/expires or crashes during editing a draft entity and the page is reloaded, the user is presented with a browser confirmation asking if they wish to reload the local backup version - "A local backup was recovered for this entry, would you like to use it?"
When selecting Yes the edit page briefly loads the unsaved backup version before automatically reloading the page again. Upon the reload, the restored version is replaced with the last saved version content.
The workaround right now is to quickly select content and copy to the clipboard before the page reloads.
To Reproduce
Steps to reproduce the behavior.
Expected behavior
When selecting to restore un-saved changes, the page should load the locally backed-up version and persist these changes until the user either clicks save or discards the changes by choosing to leave the page intentionally
Applicable Versions:
CMS configuration
Additional context
Using editorial workflow
Using Jekyll as pre-rendering engine
The text was updated successfully, but these errors were encountered: