You can't disable versions control because a temporary version is created as draft version while editing object. So if you will set VersionHistory=1 you will not be able to edit object.
You can limit versions to min 2 in content.ini configuration file or enable DeleteDrafts, for automatic draft deletion.
Look also on: http://ez.no/products/ez_publish_cms/documentation/incoming/remove_confirmation_when_discarding_an_object
Well, but I do not want to limit version control. In fact because of all these unintented drafts I have had to increase the number of versions from 10 to 20 - otherwise the "real" drafts and the real versions of pages get lost between the uninteded drafts. The ideal would be if you could specify separately the number of real version and the number of drafts.
What does enable DeleteDrafts do ? And is it possible as an administrator to delete old drafts ?
I agree with Helle. Our users are also not so very happy with the case that every time they edit a page, a new draft is created. And you've right..the important drafts just dissapear because of this.
There should be options: - ..if a user has modified an existing object, then he/she should get the option to overwrite the published object, or publish, but archive the old published one, and publish the newer one ++
..this is not so hard to change in the eZ publish code, but it should be default in the eZ publish code.
I've made a hack to automatically remove drafts that haven't been changed. It's in pubsvn: http://pubsvn.ez.no/community/trunk/hacks/untoucheddrafts. Currently we're still testing it at one of our portals, but I would be happy if other people already give it a try.
I think I found the apropriate sollution for this problem. I started inspecting some eZ code in order to find the sollution and came accross an interesting INI setting...
Just put:
EditDirtyObjectAction=usecurrent
in your site.ini (in overrides or siteacces) and automatic Drafts are disabled.