User Tools

Site Tools


how-do-i-view-the-revision-history-of-a-page

How do I view the revision history of a page?

Draft. A page revision history is not documented. The Content > Pages field list does not include history, compare, or restore. Do not follow steps that tell you to open “Revisions” or to roll a page back. Those controls are verification required in the live admin. What is documented is an admin audit log, plus a NOTES field on A/B variations. Neither one is a restorable copy of the page body.

Before You Begin

Log in with an account that can open the page and Logs > Logged Actions. Restricted users may not see the log. Verification required: which permission that is.

Ignore the wiki page how-do-i-edit-an-existing-page if it says every save creates a revision you can restore at any time, or that history is auto-saved every 30 seconds. That page also says to use Content → All Pages, Save Draft, Update, and Schedule. The Pages reference instead says the left side of the Pages module lists pages, and page status is Active(Published) or Disabled(Suspended). Where those two pages disagree, this article follows the Pages reference and does not treat rollback as a feature.

The frontend toolbar in CMS 5.8.9 opens the current page for editing. It is not described as a history browser.

Step-by-Step Instructions

What you can do with documented tools

  1. Open Content > Pages and select the page in the left list.
  2. Use the editor's source view if you need to read the current HTML. The Pages article says the content area is a WYSIWYG editor with source viewing.
  3. If the page is an A/B test, read the NOTES field at the top of each variation. Getting Started says NOTES is where you remind yourself what you changed. It is a note, not an old copy of the page.
  4. Open Logs, then Logged Actions, when you need to know who did something. The log stores time, IP address, username, and the action. Verification required: whether a page-edit action includes the before-and-after body. The written page does not say it does.
  5. You can subscribe to email notifications for admin actions under Logs > Notifications. That is an alert, not an archive of page HTML.

What not to do until the control is confirmed

  1. Do not click through another product's revision list.
  2. Do not promise an editor that you can restore yesterday's page.
  3. Do not treat a disabled page as a backup. Disabled(Suspended) changes publication status. It is not documented as freezing a previous body.

Verification required: on a staging page, save a one-line change and look for a history, versions, or revisions control on the page screen and in the page list. If the control exists, write down its label and whether it can view, compare, or restore. Publish that label only after you see it. If it does not exist, the rest of this article is the operational guidance.

Example

An offer page went live with the wrong price. The editor asks for “the version from this morning.”

Open the page and read the current source. Open Logged Actions and find that username and time. You may learn who saved the page. You may not get the old price back from that row, because the log article never says the old HTML is stored.

Check NOTES on each A/B variation in case the price test was written down. If NOTES is empty and no revision control is on the screen, the old price has to come from a copy someone saved outside CBSplit. See How do I back up my CBSplit data?. There is no documented restore button to press.

How to Verify

  1. For the audit log: the row shows time, IP address, username, and an action. That is the documented result.
  2. For NOTES: the text you typed is still at the top of that variation.
  3. For a real revision feature: you can open an older body and read it without changing the live page. That result is not documented, so do not report it as done until the control has been seen.
  4. Comparing two versions and restoring one are separate actions. Viewing a log row is not a compare, and it is not a restore.

Troubleshooting

There is no Revisions button

That matches the published Pages article. Use the source view, NOTES, and Logged Actions. Ask CBSplit support before you tell the team that history is missing from a broken install. It may never have been part of this module.

Logged Actions shows the edit and not the old paragraph

The documented columns are time, IP, username, and action. A missing paragraph is not a failed restore. The body was not promised.

Two editors overwrote each other

The log can show both usernames and times. It does not document a merge. Coordinate in the NOTES field of a variation, or keep an external copy. Verification required: whether the editor warns when someone else has the page open.

Restore brought back the wrong variation

Do not attempt a restore that is not in the UI. A/B variations are alternate pages in a test, with their own NOTES. Setting a winner, which Getting Started describes as an autopilot or a manual choice of the live primary page, is a test outcome. It is not a historical rollback.

The toolbar history is empty

The frontend toolbar is an edit shortcut. It is not documented as revision history.

Frequently Asked Questions

Can I compare two versions of a page?

Not with a documented control. Verification required: check the page editor before you document a diff view.

Can I restore a previous version?

Not from any step in the Pages article or the Logged Actions article. Do not advertise rollback until the restore control is confirmed.

Does every save create a revision?

That claim appears on an conflicting how-to page and is not in the Pages reference. Treat it as unverified.

Is the admin log a backup?

No. It records that an action happened. Backup scope is a separate question, and no backup module is documented.

how-do-i-view-the-revision-history-of-a-page.txt · Last modified: 2026/11/08 08:45 by stephan