How to create version of the current page

[Mshaji]

In the siteadmin open page action, I am trying to create a version of the page before opening.

How do I create a version using js in SiteAdmin.Actions.js

[smacdonald2008]

Could you not just use the JCR API to create a node in that represents a page in the location where you want it? After all - a page is just a node. 

[Mshaji]

I want the similar functionality that we see on Sidekick version, I think that is done through js.

As soon as Author clicks open from siteadmin it will create a new version and lock the page for that author.

Author can make the changes to the page and save it, however they have open to rollback all the changes

In case of rollback, we delete the version of the page.

Thanks

Mohammed Ahmed

[smacdonald2008]

This is a unique use case. What about creating an AEM workflow that knows how to do this. Kick off the workflow via an API call and have the workflow perform the page operations that you need. I will pass this to Will. He may have some suggestions. 

[Jörg_Hoh · Accepted solution]

Hi,

Hm, that requirement seems a bit weird; even if I just want to check the content of a page on authoring, a new version is being created and the page is locked. How do you plan to unlock it again? Is the editor supposed to unlock the page after the changes? What do you want to do with the number of versions you create? Be aware, that you have to store and maintain them, and it can really become a driver for disk space.

kind regards,
Jörg

[Mshaji]

Authors have options to lock, unlock and discard on the pages. We have to maintain the versions until there is a need to clean the disk space. If this becomes bottle neck we might have to come with purge workflow to cleanup disk space at regular intervals.

[Jörg_Hoh]

Hi,

ok, but be aware, that only the owner of the lock (or admin) can unlock a page. If a user forgets to unlock a page and then goes on holiday, you always need to call the person owning the admin account, which is kind of restrictive to editors (and a burden to the admin person). The majority of projects I was at were not using locking in daily business, but only when it was a hard requirement. They prevent 2 users changing the same page by some organisational rules (which they needed anyhow).

kind regards,
Jörg

[Mshaji]

Yes, those are administrative overheads for this implementation