Skip to main content

Overview

EcomWize tracks every change you make to your page, giving you two levels of history management:
  1. Undo/Redo — Step backward and forward through individual changes within your current editing session
  2. Page versions — Save named snapshots of your page that persist across sessions and can be restored at any time

Undo and redo

Keyboard shortcuts

ActionWindows / LinuxMac
UndoCtrl + ZCmd + Z
RedoCtrl + YCmd + Y

Toolbar buttons

You can also click the undo and redo buttons in the top toolbar of the builder. The buttons are grayed out when there is nothing to undo or redo.

What gets tracked

Every section-level change is recorded as a new state in the history:
  • Adding a section to the page
  • Updating a section (changing text, images, colors, layout options, or any configuration)
  • Deleting a section from the page
  • Reordering sections (dragging to a new position)
  • Duplicating a section
  • Pasting a section from the clipboard
Each undo step reverses one of these changes, and each redo step re-applies it.
Some changes are intentionally excluded from history to keep the experience smooth. For example, color picker dragging (the intermediate states as you drag through colors) does not create history entries — only the final color selection is recorded.

History limit

The undo/redo history stores up to 50 states. Once you exceed 50 changes, the oldest states are discarded to keep memory usage manageable. This means if you have been making changes for a while, you may not be able to undo all the way back to the very beginning of your session. For long-term restore points, use page versions instead.
If you are about to make a significant change and want to be able to get back to your current state later, save a page version before making the change. Versions are not affected by the 50-state limit.

History reset

The undo/redo history resets in certain situations:
  • When you restore a page version, the history is cleared and starts fresh from the restored state
  • When you reload the page or navigate away and come back, the session history is lost
This is normal behavior. Use page versions for changes you want to be able to restore across sessions.

Page versions

Page versions are persistent snapshots of your entire page that are saved to the database. Unlike undo/redo history, versions survive across browser sessions and can be restored days or weeks later.

Opening the history panel

Click the History icon (clock icon) in the sidebar to open the history panel. This panel shows all saved versions for the current page.

Saving a version manually

1

Open the history panel

Click the History icon in the sidebar.
2

Click Save Version

Click the Save version button at the bottom of the panel. A snapshot of your current page (all sections and their configurations) is saved immediately.
3

Confirm the save

A toast notification confirms that the version was saved. The new version appears in the list with a timestamp and the label “Manual”.

Auto-periodic versions

EcomWize also saves versions automatically at regular intervals while you are editing. These versions are labeled Auto in the history panel to distinguish them from your manual saves. Auto-periodic versions are created:
  • Periodically while you are actively editing (only if changes have been made since the last backup)
  • As a safety net so you do not lose work even if you forget to save manually
Auto-periodic versions count toward your version limit. If you want to keep a specific state long-term, save a manual version so you can easily identify it later.

Previewing a version

Before restoring a version, you can preview it on the canvas to see what the page looked like at that point in time:
1

Click on a version

In the history panel, click on any version entry. The canvas will load that version’s sections so you can see the page as it was when the version was saved.
2

Review the preview

Scroll through the page on the canvas to review the version. A banner at the top of the history panel indicates that you are previewing a past version.
3

Cancel or restore

You have two options:
  • Cancel — Click the cancel button to return to your current page. Your current work is restored exactly as you left it.
  • Restore — Click the restore button to permanently replace your current page with this version.
Restoring a version replaces your current page content with the version’s content. Your undo/redo history is reset after a restore. If you want to keep your current state, save a manual version before restoring an older one.

Deleting a version

To delete a version you no longer need:
  1. Hover over the version entry in the history panel
  2. Click the trash icon
  3. Confirm the deletion in the dialog that appears
Deleted versions cannot be recovered.

Version limit

Each page can store up to 20 versions. When you save a new version and have already reached the limit, the oldest version is automatically deleted to make room. This limit applies to the combined total of manual and auto-periodic versions.

Version details

Each version entry in the history panel shows:
DetailDescription
TimestampWhen the version was saved (e.g., “Feb 14, 2:30 PM”)
Section countHow many sections the version contains
TypeWhether the version was saved manually or automatically (“Auto”)

Current version indicator

At the top of the version list, a green pulsing dot indicates the current version — the live state of your page. This is always shown above the saved versions so you can see how many sections your current page has compared to past versions.

Best practices

If you are about to redesign a section, change your brand style, or restructure your page, save a manual version first. This gives you a clear restore point if the changes do not work out.
For small mistakes like accidental deletions or typos, use Ctrl/Cmd + Z to undo quickly. It is faster than navigating to the history panel.
Since you are limited to 20 versions, delete versions you no longer need to make sure important snapshots are not pushed out by the auto-save system.
Always preview a version before restoring it. This lets you verify it contains the state you want without committing to the change.