Version Manager in 5.6.1 | Community
Skip to main content
A
askdctm
October 16, 2015
Solved

Version Manager in 5.6.1

  • October 16, 2015
  • 2 replies
  • 791 views

Hi All,

In https://docs.adobe.com/docs/en/cq/5-6-1/deploying/version_purging.html#Version Manager it says

"In addition to explicit purging by means of the purge tool, the Version Manager can be configured to purge old versions when new versions are created."

Can you please let me know as to how, this can be configured as I am unable to find it in OOTB instance[OSGI-> Configurations]

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by WhoaShekhar

Hi there,

Thanks for reaching out.

Please go through the below link for version purging :

To configure the Version Manager, create a configuration for:

    PID com.day.cq.wcm.core.impl.VersionManagerImpl

The following options are available:

  • versionmanager.createVersionOnActivation (Boolean, default: true)
    whether to create a version when pages are activated.
    A version is created unless the replication agent is configured to suppress creation of versions, which is honoured by the Version Manager
    A version is only created if the activation happens on a paths that is contained in versionmanager.ivPaths (see below).
  • versionmanager.ivPaths (String[], default: {"/"})
    paths on which versions are implicitly created on activation if versionmanager.createVersionOnActivation is true.
  • versionmanager.purgingEnabled (Boolean, default: false)
    whether to enable purging when new versions are created
  • versionmanager.purgePaths (String[], default: {"/content"})
    on which paths to purge versions when new versions are created
  • versionmanager.maxAgeDays (int, default: 30)
    on purge, any version older than this value will be removed. 999999 or any other high value can be used to ignore this parameter
  • versionmanager.maxNumberVersions (int, default 5)
    on purge, any version older than the n-th newest version will be removed. 999999 or any other high value can be used to ignore this parameter

 

Thanks!

2 replies

WhoaShekhar
WhoaShekharAccepted solution
October 16, 2015

Hi there,

Thanks for reaching out.

Please go through the below link for version purging :

To configure the Version Manager, create a configuration for:

    PID com.day.cq.wcm.core.impl.VersionManagerImpl

The following options are available:

  • versionmanager.createVersionOnActivation (Boolean, default: true)
    whether to create a version when pages are activated.
    A version is created unless the replication agent is configured to suppress creation of versions, which is honoured by the Version Manager
    A version is only created if the activation happens on a paths that is contained in versionmanager.ivPaths (see below).
  • versionmanager.ivPaths (String[], default: {"/"})
    paths on which versions are implicitly created on activation if versionmanager.createVersionOnActivation is true.
  • versionmanager.purgingEnabled (Boolean, default: false)
    whether to enable purging when new versions are created
  • versionmanager.purgePaths (String[], default: {"/content"})
    on which paths to purge versions when new versions are created
  • versionmanager.maxAgeDays (int, default: 30)
    on purge, any version older than this value will be removed. 999999 or any other high value can be used to ignore this parameter
  • versionmanager.maxNumberVersions (int, default 5)
    on purge, any version older than the n-th newest version will be removed. 999999 or any other high value can be used to ignore this parameter

 

Thanks!

A
askdctmAuthor
October 16, 2015

Hi,

Thanks a lot for your reply. I tried out few things with "Apache Sling Logging Logger configuration", but looks like I am not doing it correctly.

1] But I am not getting as to how the below is to be done

"create a configuration for: PID com.day.cq.wcm.core.impl.VersionManagerImp".

2] Also, what exactly is this "PID"?

Your thoughts on this will be helpful.

Terms & ConditionsAccessibility statement

Loading footer...