Revisions

MageDrop automatically tracks every save made to CMS pages and blocks in your Magento store. Each save creates a revision — a full snapshot of the entity's state at that point in time. You can browse the complete history of any entity and roll back to any previous version with one click.

How revisions work

When the MageDrop companion module is installed and enabled, it observes every CMS page and block save in the Magento admin. After each save, the module sends a snapshot of the entity's data to MageDrop, where it's stored as a revision.

This happens automatically — no extra buttons to click, no workflow changes. Every time anyone on your team hits save on a CMS page or block, a revision is captured.

Initial sync

Revisions are only captured going forward from when the module is installed. To create a baseline snapshot of all your existing CMS content, you can run an initial sync:

• During setup — after connecting the module, step 3 of the setup wizard offers a "Sync Now" button that captures all current CMS pages and blocks.
• From the Revisions tab — click Sync from Magento at any time to pull a fresh snapshot of all entities. This is useful if new pages or blocks have been created outside of the module's tracking.

Each sync creates a new revision snapshot for every CMS page and block. These are labelled "Imported from Magento" in the revision timeline. You can run the sync as many times as needed.

What gets captured

Each revision includes:

• All scalar fields — title, content, identifier, meta title, meta description, status, and every other non-array field on the entity
• Admin username — the Magento admin user who made the save
• Timestamp — exactly when the save occurred
• Entity type and ID — which CMS page or block was saved

Viewing revisions

To browse revisions for a store:

1. Navigate to your store in the MageDrop dashboard.
2. Click the Revisions tab (next to the Releases tab).
3. You'll see a list of all CMS pages and blocks that have revisions, ordered by most recently changed.

Each entity shows:

• The entity title and type (CMS page or CMS block)
• The Magento entity ID
• The total number of revisions
• When the latest revision was captured

Entity revision history

Click on any entity to see its full revision timeline. Each revision shows:

• Whether it was a normal save or captured before a revision rollback
• The date and time of the save
• The Magento admin user who made the change
• The number of fields captured

Revision detail view

Click View on any revision to see the full snapshot data. The detail view shows every field and its value at the time of that save.

If a previous revision exists, fields that changed between revisions are marked with a dot. Click any row to open a diff view showing the previous and current values side by side.

Rolling back to a revision

You can restore any entity to a previous revision's state. This pushes the revision's data back to Magento via the REST API.

1. Navigate to the entity's revision history.
2. Find the revision you want to restore to.
3. Click Rollback (from the history list) or Rollback to This (from the detail view).
4. Confirm the action.

What happens during a revision rollback

1. Current state is captured — before making any changes, MageDrop snapshots the entity's current state from Magento. This creates a new revision so the rollback itself can be undone.
2. Revision data is pushed — the selected revision's field values are sent to Magento via a PUT request to the REST API.
3. Activity is logged — the rollback is recorded in the store's activity log.

The entity is updated immediately on the live store.

Undoing a revision rollback

Because MageDrop captures the current state before each rollback, you can always undo a revision rollback. Simply go back to the entity's revision history and roll back to the revision that was automatically created before the rollback (labelled "Before revision rollback").

Revisions vs release rollback

MageDrop has two different rollback mechanisms that serve different purposes:

Use release rollback when you want to undo a coordinated set of changes. Use revision rollback when you want to restore a single entity to a specific point in time — for example, undoing someone's accidental edit.

Revision storage

Revisions are stored in the MageDrop database, not in your Magento instance. This means:

• No additional database tables or bloat in your Magento store
• Revisions are accessible from the MageDrop dashboard regardless of what happens to your Magento database
• The Magento companion module has no impact on save performance beyond a single background API call

Best practices

• Revisions are automatic — once the module is installed, every save is captured. You don't need to do anything special.
• Use revisions for single-entity recovery. If someone accidentally broke a page, find the last good revision and click rollback.
• Use release rollback for coordinated changes. If a whole release needs to be undone, use the release rollback instead of reverting entities individually.
• Check the diff before rolling back. Click View on a revision to see exactly what the entity looked like at that point. Compare it against the current state to make sure it's the version you want.