Publishing
History and restoring a version
See what is live, review every earlier published version, and go back with Restore and publish or Restore as draft without ever losing history.
Last updated
Every time you publish, Ulika keeps a version of your site's content. The History screen shows what is live, what is waiting to go live, and every earlier published version, so a bad change is never permanent. Restoring a version never deletes anything: it adds a new version on top.
Open History#
Open your project and choose History in the project navigation. The page says "What is live on your site, what is waiting to go live, and every earlier published version you can go back to."
What you see#
Unpublished changes#
If you have saved edits that are not live, a highlighted block titled Unpublished changes says, for example, "3 changes saved, not live yet. Your site still shows the version marked Live now." Click Hide or Show to collapse or expand the list of before and after values.
Published versions#
The list Published versions has one card per publish, newest first:
"Published by" the person's name.
A green Live now badge on the newest version, which is what visitors see.
When it happened (hover for the full date and time) and "3 changes" (or "First version" for the first one).
See what changed (and then Hide changes) shows each edit as the old value crossed out, an arrow, and the new value. Images are shown as small before and after thumbnails.
Restore this version on every card except the live one, if your role allows it.
Before anything has been published it says "Nothing has been published yet. Once you publish, each version appears here and you can go back to any of them."
All activity, including every edit#
At the bottom, a folded section called All activity, including every edit holds the full log. It has filter tabs with counts: All, Edits, Publishes and Restores. Each row has a colored badge for its kind:
| Badge | What it records |
|---|---|
| Edit | A change saved in the editor. |
| Publish | A publish that went live. Shows its reference. |
| Restore | A restore from an earlier version. |
| Media | A change to the media library. |
| Collection | A change to collection items. |
| SEO | A change to page search details. |
| Detection | A scan of your site that found or updated editable content. |
Rows have View (the changes in a dialog) and Restore. The screen loads the most recent 200 versions.
Restore this version#
Click Restore this version on a published version. The dialog Restore this version? says "Your site will go back to how it looked on" followed by the date, and reassures you: "You can undo this: going back is added to your history as a new version, and every version stays here so you can return to any of them."
If you have unpublished changes it also warns "Your 3 unpublished changes will be replaced by that version." The dialog offers three buttons:
| Button | What happens |
|---|---|
| Cancel | Nothing. |
| Restore as draft | The old content is copied into your draft. Your live site does not change. You see "Restored as a draft" and "Your site has not changed yet. Publish when you are ready." Review it in the editor, then publish when you are happy. |
| Restore and publish | The old content becomes the draft and is published straight away through the normal publish flow. A progress banner shows "Building your site…" and then "Live on your website". |
The text in the dialog says it plainly: "Prefer to look first? Restore as draft brings it into the editor without changing your live site."
What you see after Restore and publish#
When the early layer or the rebuild is live: "Live on your website" and "Your site now looks like it did on" followed by the date, with "Search engines update in about 30 seconds."
When the rebuild finishes after that: "Your site is back to how it looked".
If the restored content already matches what is live: "Your site already looks like that".
If the restore worked but publishing did not: "Restored as a draft, but it could not be published:" followed by the reason. The content is in your draft, and you can publish again from the editor.
If Ulika cannot confirm the new version is live: "Publication not confirmed". See When a publish fails.
Restore from the activity log#
In All activity, including every edit, Restore on a row opens the same dialog but with one action, Restore version, which restores to the draft only. The dialog says: "Restoring copies that version's content back into your draft and appends a new version describing what moved. Nothing is deleted. This entry and everything after it stay in the history. Production keeps serving what it serves today until someone publishes the restored draft." The result is "Restored 12 values. A new version records the change." or, when nothing differed, "The draft already matched that version. No values changed, and the restore is logged."
What a restore changes and what it does not#
It restores content values: text, links, images, page search details, and the looks you set in the style panel.
It restores deleted collection items as drafts when the old version holds enough to rebuild them, and skips content that no longer exists in your site's code.
It does not touch your site's code or your repository.
It never removes a version. Restoring a restore is normal.
A look is only restored if it is still valid for the style rules.
Who can restore#
Restoring needs the restore version permission. Both the owner and editor roles have it, and viewers do not (the restore buttons are hidden for them). Restore and publish also needs the publish permission, which owners and editors have too. See Roles.
Was this page helpful?