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
{{ message }}
Repository navigation
Restore an entry to a previous version from the History panel
#1024
The entry sidebar's History panel lists previous saves, but clicking one opens the commit on GitHub. For the non-technical clients I hand sites to, it would confuse them: they don't know GitHub, and restoring means finding the file in the commit and copying each field back by hand. In practice they have to ask me to do it.
A 'Restore this version' action on each item in the History panel. It would load that version's content into the editor as unsaved changes, so the editor can check it in the preview and then click Save (or Revert All Changes to back out). The restore would then just be a normal new commit, so nothing in the history is lost.
A Compare with current view would be a nice extra, but loading the old version into the editor with the live preview already goes a long way.
Additional context
I'm moving small-business client sites from WordPress to Astro + Sveltia. The editing experience, especially with a custom live preview, is the best I've found for clients. Being able to undo a bad save themselves is the main thing they miss from WordPress's revisions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The entry sidebar's History panel lists previous saves, but clicking one opens the commit on GitHub. For the non-technical clients I hand sites to, it would confuse them: they don't know GitHub, and restoring means finding the file in the commit and copying each field back by hand. In practice they have to ask me to do it.
A 'Restore this version' action on each item in the History panel. It would load that version's content into the editor as unsaved changes, so the editor can check it in the preview and then click Save (or Revert All Changes to back out). The restore would then just be a normal new commit, so nothing in the history is lost.
A Compare with current view would be a nice extra, but loading the old version into the editor with the live preview already goes a long way.
Additional context
I'm moving small-business client sites from WordPress to Astro + Sveltia. The editing experience, especially with a custom live preview, is the best I've found for clients. Being able to undo a bad save themselves is the main thing they miss from WordPress's revisions.
All reactions