Magnolia versions pages, assets and contacts by default when they are published and unpublished. You can also configure versioning for any other content type.
The Show versions action provides access to versions. This action is available in the Pages, Assets and Contacts apps and opens a dialog containing a list of versions.
|If workflow is enabled, the workflow comment is appended for each version (second set of brackets).
To show a version, select the version and click Show. The selected page, asset or contact opens for viewing.
|You cannot edit the item in the view mode.
In the Pages app two additional actions are available:
Compare to previous version compares the current to the previous version and opens the page in diff view that uses redlining: deletions are highlighted in red and insertions in green.
Compare versions allows you to select the versions to be compared. Select a From and To version and click Compare to open the page in diff view.
The Restore versions action allows you to revert to a previous version. It is available in the Pages, Assets and Contacts apps. Select the version and click Restore. A new version is created automatically prior to restore. After restoring you need to publish the restored item.
Restoring a previous version does not restore the name or location (path) of the item if these have been changed.
Versioning functionality is enabled by default in Magnolia in the Pages, Assets and Contacts apps. Versions are saved automatically and can be reverted to as necessary.
The versioning functionality is enhanced by the Diff module that adds diff and redlining capabilities.
By default, versions are created when pages, assets and contacts are published, unpublished and restored in the related apps. Versions are also created in these apps for the purpose of restoring items prior to deletion.
For more information, see Deleting and restoring.
|Versioning can be enabled by configuration for any content app.
In a new installation of the Magnolia bundle all demo pages, assets and contacts do not have versions even though the status indicator is green (published). This is because the content is marked as published when bootstrapped into the web applications, but no actual publication has taken place at this point in time. The available versions actions remain inactive until actual versions are created by publishing, unpublishing or deleting.
Versioning is functionally usable only on the admin instance, where you can use it to restore and republish an older version of some content. In case you wanted to let the visitors of your site browse through and see historic versions of, for example, a terms and conditions page, you would have to develop custom code for this feature.
You can limit the number of versions held in your repository using the Configuration app.
|Each time you create a new version of an item in Magnolia, Magnolia creates a copy of the entire item and not just a delta from the previous version. Because of this, we recommend limiting versions if possible. Otherwise, the version store will grow quickly which can inhibit performance.
Start up your Magnolia instance.
Under Apps, go to Configuration app.
Navigate down to server > version.
Edit the property.
Input your desired Value. This defines the maximum number of versions allowed.
Don’t forget to save your changes.