Versioning and history
How autosave, version history, and rollbacks work across Basker content
Basker keeps a version history of most content. Every save creates a version; older versions are retained so you can see what changed, who changed it, and roll back if you need to.
What's versioned
Almost everything you edit in Basker is versioned. Pages, events, posts, people, venues, announcements, and most other content types track their full history. Some operational records (like media files or settings) keep a simpler audit trail rather than full version history.
If you can save a record as a draft and publish it, it's versioned.
Autosave
Basker saves your work as you go, so you don't need to manually save in the middle of an edit. Edits are kept as draft state, separate from the published version on the live site, until you publish the change.
When your browser closes or you navigate away mid-edit, your in-progress work is preserved as the latest draft. Open the record again and you'll resume from where you left off.
Viewing version history
Each record has a Version history option that lists past versions in reverse chronological order, newest first. Each entry shows:
- When the version was saved.
- Who saved it.
- Whether it was a draft, an autosave, or a publish.
Click a version to view its content as it stood at that point.
Comparing versions
Open two versions side by side to compare them. Differences are highlighted so you can see exactly what changed between, for example, last week's published version and the current draft.
Rolling back
To roll back to an earlier version, open the version you want to restore and choose Restore this version. Basker creates a new draft from the older version's content. Review the draft, then publish it normally to make the rollback live.
Rollbacks never overwrite history. The version you restored from stays in the record's timeline, and the new draft is added on top — so you can see exactly when and why a rollback happened.