You need to have
content remove Owner( Self )
content versionread Owner( Self ) to delete versions.
VersionHistoryClass[1]=5 means that for class 1 ( folder in standard eZ publish ), the maximum exising version amount is 5.
The system will try to delete the oldest archived version if it can't create a new version. If you got waring "Could not make new version.The limit for versionhistory is exceeded, og no archived versions can be removed by the system", then the system cann't find archived version. Since it is not a good choice to delete a draft ( maybe belongs to other user), the system will issue the warning and let user to deceide to delete which draft.
I got the role-settings perfect:
content remove Section( xxx ) , Owner( Self ) content versionread Section( xxx )
BUT: the user in this role still don't get the checkbox for deleting
versions in versionadministration. That's our problem. So I(the admin) have to log in, and delete the versions for them, when they get the error message when the limit is
exceeded. I can increase the limit in settings, but don't want to have to many versions in the system...so is this a BUG?
I think the best solution would be if there are no more archived versions, then start to delete the drafts. It's very CRITICAL when the user is not able to edit and publish their content, and also don't have the rights(because of a bug) to delete the versions.
What kind of publishing-society is that, hehe :p A very strict one ;) "Your version history is exceeded, so you don't have any more credit to publish" ;)
Best regards.
You must be logged in to post messages in this topic!