Forums / Suggestions / Being able to limit the number of versions available
francis Nart
Wednesday 17 March 2004 2:16:54 am
We think it would be a good point to have a way to limit the number of versions an object should keep. This way, when dealing with an e-commerce site where you have multiple versions of the products (change of reference number, price...) it could maintain the number of versions to a reasonable limit and disc
Kåre Køhler Høvik
Wednesday 17 March 2004 2:28:37 am
In content.ini you can set
[VersionManagement]DefaultVersionHistoryLimit=10
--Kåre Høvik
Kåre Høvik
Paul Forsyth
Thursday 18 March 2004 4:00:46 am
When i last tried this, with 3.2, i found the minimum number of versions is 2. The reason back then was that eZ needed to first create a new version in order to populate it. If the number was set to 1 it was impossible for the system to create a new version, which confused eZ. Im not sure if this has been resolved with 3.3
paul
Thursday 25 March 2004 8:22:14 am
great news !
I just decided to print the entire content.ini file to find other "good news" like this one (I hope !).
Lauren Matheson
Monday 05 April 2004 9:07:38 pm
Is there a way to set this based on class or section? It would be great to keep many or all versions of important data, and few of others.
Balazs Halasy
Monday 05 April 2004 11:47:51 pm
As far as I know: this is a global setting, it goes for all content (the entire tree) - can't be set on a section/subtree basis.
Balazs
Script start
Module start 'content'
Module end 'content'
Script end
Time used to render debug report: 0.0002 secs