Adobe Experience Manager Sites & More

johndoe42 · 1/30/17

Hi guys

I have a quick question regarding version purging. According to [0] I should use the Version Manager (PID com.day.cq.wcm.core.impl.VersionManagerImpl). Yet there is also a configuration for the Version Purge Task (PID com.day.cq.wcm.core.impl.VersionPurgeTask) which according to [1] is part of the maintenance tasks. Do I understand it correctly that the Version Manager can be used to clean up old versions whenever a new version gets created. However when no new version gets created it will not remove old versions. That's why we have to run the Version Purge Task periodically to make sure the age limits are met. Is this correct?

And one more question. According to [2] it is possible to disable versioning on the publish altogether. Could someone please explain to me how this is done. I couldn't find such an option. Would it be sufficient to set the "Implicit Versioning Paths" in the Version Manager to a non-existent path or leave it empty to achieve this?

Any help is much appreciated.

Cheers

[0] https://docs.adobe.com/docs/en/aem/6-2/deploy/configuring/version-purging.html

[1] https://docs.adobe.com/docs/en/aem/6-2/administer/operations/operations-dashboard.html

[2] https://www.netcentric.biz/blog/maintenance-in-aem-6-with-crx3-tarmk.html

kautuk_sahni · 1/30/17

Hi

Do I understand it correctly that the Version Manager can be used to clean up old versions whenever a new version gets created.

If we use Version manager, then it is true. But you can explicitly purge it by Purge Version Tool. Here for Pure Version tool, you can specify path, Max Version to keep and Max Age. And then you may purge versions without creating new one.

For Disabling version purging :- https://helpx.adobe.com/experience-manager/kb/DisableVersioning.html

// change <limits default="-1"> to <limits default="0">

~kautuk