Vai al contenuto

Content history: going back after a bad edit

Since 26.3 CMS pages, blocks and blog posts keep their versions: open the Versions tab, look at a preview and restore, without losing the state you start from.

Anyone who works on content knows the moment: somebody opens a CMS page, changes three lines, saves, and finds out those three lines were holding the whole page together. Without history you rebuild from memory, and memory has no undo button. Since 26.3 Maho keeps a version of every save of a content record, and restoring is one click.

What is tracked

The module covers three content types, the ones edited most often and damaged most easily:

  • CMS pages;
  • CMS blocks;
  • blog posts.

The rest of the store, products included, has no history: that stays with the logs and the backups.

Where to look

Open the record you care about, for instance from CMS > Pages. Under the fields sits the Versions tab, titled Content Version History. Inside is the grid of saves, most recent first.

✏️ Marginal note: the tab is not there on a brand new record, because there are no versions yet. It appears after the first save, which is also the moment it starts to matter.

Preview before restoring

Every row carries two actions: preview and restore. The preview shows what the content looked like in that version without applying it. That is what separates a useful history from a risky button: first you look, then you decide.

What a restore actually does

A restore writes the content of the chosen version back into the page, the block or the post. The state you started from is not lost: it is saved as a new version, stamped with the moment. So even a wrong restore can be undone by restoring the version before it.

✏️ Marginal note: the history is not a git branch. There are no merges between versions, you go back to a state and continue from there. For real parallel work the repository is still the right tool.

How many versions to keep

Two settings live in System > Configuration > General > Content Versioning:

Setting What it does
Max Versions Per Entity versions kept per record, 0 means no limit
Max Version Age (Days) deletes versions older than that many days, 0 means no limit

On a catalog of content that changes often, the count limit is the one that keeps the table in check: a hundred versions of a page are useful, a thousand are just weight. The age limit fits seasonal work: thirty days cover a mistake found late, ninety cover a legal review.

✏️ Marginal note: set both limits to zero and the history grows forever. That is a legitimate choice on a store with a handful of pages, less so on one that publishes daily.

The practical case

On Friday afternoon an urgent change lands on the shipping page. On Monday the owner asks why the returns paragraph is gone. Open the page, go to Versions, find Friday morning, preview it, confirm the paragraph is there and restore. The text comes back, the urgent change stays in the history, and nobody has to rebuild anything.

On a store with more content, the same route lets you compare two drafts of a block before a campaign without touching the published version.

Text prepared with the help of AI and checked against the source before publication. It can still contain mistakes: if you find one, report it.Read the manifesto

Does your store still sell?

Tell us where you are starting from: we reply with a first assessment, no strings attached.

Ask for the store assessment