Jahia CMS includes with a versioning system based on the JCR API. The versioning system has two different behavior, one for files (binaries) and another one slightly different for other content types.
On files every time you upload a file with the same name, Jahia offers the possibility to create a new version of this file so you can always restore an older version or access it. For content there is no version in the default workspace, versions are only created when publishing this content.
When you publish a batch of content or files, Jahia increments the version of the impacted elements (mainly all the modified contents that are part of this batch of publication).
To see how it works, import the prepackaged demo site in Jahia and publish everything.
The restore function is only available on a content level, you can not restore a whole page directly to a certain state. Pages are much more complexed objects than what meets the eyes (If we restore a page what do we do of its child pages, do we restore also the templates, etc.)
You can display any version of an URL by passing a date (in a long format) as a parameter http://localhost:8080/jahia/cms/render/default/en/sites/ACME/home.html?v=1305815700000 Jahia 6.6 will retrieve the state of the content at this date and all displayed content we will be displayed at this date (files, etc.) the only exception is the queries that will return results from the present and not from the past, indexes have no version.
When you restore a file this will automatically create a new version, like you have uploaded a new version. This is not the case for the content, the only versioning on content is on publication.
Copyrights © 2002-2020 All Rights Reserved by Jahia Solutions Group SA