Details
-
Bug
-
Resolution: Duplicate
-
Medium
-
None
-
4.5.0
-
None
-
eZ Publish 4.5
Description
According to the http://doc.ez.no/eZ-Publish/Technical-manual/4.x/Reference/Configuration-files/content.ini/VersionManagement/VersionHistoryClass VersionHistoryClass and http://doc.ez.no/eZ-Publish/Technical-manual/4.x/Reference/Configuration-files/content.ini/VersionManagement/DefaultVersionHistoryLimit DefaultVersionHistoryLimit docs "//When decreasing "content.ini/[VersionManagement]/VersionHistoryClass" you need to run the script script "bin/php/cleanupversions.php" to remove exceeded archived versions//".
But I'm getting the opposite behavior: all versions are removed except the latest one.
Steps to reproduce
1. Set these values on your content.ini:
[VersionManagement] DefaultVersionHistoryLimit=10 VersionHistoryClass[1]=5 VersionHistoryClass[16]=15 DeleteDrafts=disabled
2. create an article, and edited it several times until you got the maximum number of versions allowed (in this case it will be 15).
3. Execute //php ./bin/php/cleanupversions.php// and nothing would change, no versions should be deleted, which is correct
4. Set //VersionHistoryClass[16]// to 14
5. Execute //php ./bin/php/cleanupversions.php// again, and all version should be removed except the latest one.
Attachments
Issue Links
- duplicates
-
EZP-18466 Changes to DefaultVersionHistoryLimit not reflected on existing objects
- Closed