Magento 2 CMS Revisions with History and Restore
SKU: CMSPAGEREVISIONS1
- every save of a CMS page or block is kept as a revision
- diff comparison of two versions with colour marks
- one-click restore, optionally for single fields only
- retention, rights and cron cleanup configurable
Einmaliger Kauf · inkl. 12 Monate Updates · zzgl. MwSt.
Magento 2 CMS revisions: every change traceable and reversible
With the Magento 2 CMS revisions module from Mironsoft, your shop stores a revision automatically each time a CMS page or CMS block is saved. Editors browse the history, compare two versions side by side and restore an earlier one with a single click. The module works in the admin without jQuery and without an extra library, and its interface follows the standard Magento look. Magento 2 CMS revisions can be switched on or off per store view and per content type and is configured in a few minutes.
Automatic revisions
Every save of a page or block creates a version with time and user.
Diff view
Two versions are compared line by line, changes in the HTML are highlighted in colour.
Restore
An older version is written back with one click, and the current state is kept as a revision.
Pages and blocks
Versioning covers CMS pages and CMS blocks, including Page Builder content.
Change note
Editors add a short note when saving, which then appears in the history.
Rights and retention
ACL rights decide who may restore, and a cron job removes old revisions.
Why editors want to trace every change in the Magento 2 CMS
By default, every save overwrites the previous content of a CMS page. Anyone who deletes a paragraph by mistake, breaks a layout or edits a legal page wrongly has no way back except a database backup. Many merchants therefore search for Magento 2 CMS revisions, a history for CMS pages or an undo function for blocks. On home pages, landing pages and legal texts a mistake quickly costs revenue or creates legal risk.
With Magento 2 CMS revisions, a final save becomes a traceable step. You see who changed what and when, and can go back to the last good version in seconds. That protects teams with several editors, agencies with client access and anyone who maintains content under time pressure.
Magento 2 CMS revisions: the history inside the page editor
With Magento 2 CMS revisions, the editor of every CMS page and block gets an extra section called Versions. It lists all saved versions with date, user, store view and change note. The list can be searched and filtered, so even pages with hundreds of revisions stay clear. A revision is created only if the content actually changed, empty saves create no entries.
- Date, user and note for each version at a glance
- Filter by period, user and store view
- No revision when the content is unchanged
Compare two versions: the diff shows every change
Pick two revisions and the module shows them side by side. Added lines are marked green, removed lines red, and changed attributes such as meta title or URL key are listed separately. You see in seconds which sentence is missing or which widget was swapped. The comparison works for HTML content as well as for Page Builder source.
- Line-by-line comparison with colour marks
- Meta fields, URL key and layout in the comparison
- Also usable for Page Builder source
Restore an earlier version without losing data
With Magento 2 CMS revisions, one click on Restore turns the chosen version into the current page content. Before that, the module saves the existing content as its own revision, so even a restore can be undone. Optionally you can bring back single fields only, for example the content but not the URL key. The full page cache of the affected page is cleared automatically.
- The current state is saved before writing back
- Restore selected fields only if you wish
- Cache of the affected page is cleared
Control retention, rights and storage space
Under Stores › Configuration you set for Magento 2 CMS revisions how many revisions are kept per page or how many days the history reaches. A cron job removes older entries so the database does not grow. ACL rights decide who may view the history, compare and restore. If you need the module only for certain pages, an exclusion list leaves out the others.
- Maximum number of revisions or retention in days
- Separate rights for viewing and restoring
- Exclusion list for pages and blocks
Where Magento 2 CMS revisions help in daily editing
Typical situations in which Magento 2 CMS revisions saves time and nerves.
Deleted by mistake
An editor removes a section of the home page while tidying up. In the history yesterday's version is chosen and written back.
Campaign pages
A landing page is rebuilt several times for a campaign. If the campaign is cancelled, the page returns to the old version.
Legal pages
When the imprint or withdrawal notice is edited, the history shows who saved which wording and when. Legal review remains the merchant's responsibility.
Agencies and teams
Several people maintain the same pages. The diff shows which change came from whom, and conflicts can be resolved cleanly.
Magento 2 CMS revisions: with and without the module
What Magento 2 CMS revisions changes compared with database backups and guesswork.
| Topic | Without module | With Mironsoft CMS Revisions |
|---|---|---|
| Undo | Only via database backup or rewriting | Restore with one click |
| Traceability | No hint who changed what | History with date, user and note |
| Spotting changes | Compare pages by hand | Diff view with colour marks |
| Database size | No control | Limited count and cron cleanup |
| Permissions | Every editor overwrites everything | Separate rights for viewing and restoring |
How we set up Magento 2 CMS revisions for you
The process after you place the order.
Alignment
You decide whether pages, blocks or both are versioned and how long the history is kept.
Installation
We install the module, enable Magento 2 CMS revisions for your store views and check compatibility with your Page Builder. From the first save on, Magento 2 CMS revisions keeps the history.
Rights
We assign ACL rights for viewing, comparing and restoring to your editorial roles.
Test
We test saving, diff, restore and cache clearing on real pages and blocks of your shop.
Handover
Your team gets an introduction to history, comparison and cleanup.
Differentiation from scheduling, import and page restriction
The CMS block scheduler from Mironsoft switches content on or off at fixed dates, the CMS block import moves blocks between systems, and the page restriction controls who sees a page in the storefront. Magento 2 CMS revisions serves a different purpose: it records the editing history and makes changes reversible.
All modules can be combined. The admin interface works without jQuery, and the module changes nothing in the storefront and loads no JavaScript there.
No download, but personal setup
CMS Revisions is not listed here as a ready-made download file to install yourself. The purchase is a commission: we contact you after the purchase, install the module in your shop and agree on retention, rights and exclusions together with you.
Frequently asked questions
Everything important about history, diff, restore and how the purchase works.
How can I roll a CMS page back to an earlier version in Magento 2?
How can I see who changed a CMS page in Magento 2?
Are CMS blocks versioned too?
How do I compare two versions of a page?
Does the database grow because of revisions?
Does Magento 2 CMS revisions work with the Page Builder?
Who may restore versions?
Does the module work with Hyvä?
How does it differ from the scheduler and import for CMS blocks?
Can I download and install the module myself?
Recently Viewed Products
Magento 2 CMS Revisions – Mironsoft