Christophe --
Thanks for testing this. Your confirmation suggests I will follow your lead.
Unfortunately, I only noticed the xwiki.cfg options that control this after
i deleted them directly from the database in SQL:
Here are the xwiki.cfg settings I'm using to achieve this:
#-# Whether the document recycle bin feature is activated or not
# xwiki.recyclebin=1
#-# Whether the attachment recycle bin feature is activated or not
storage.attachment.recyclebin=0
#-# Whether the document versioning feature is activated or not
# xwiki.store.versioning=1
#-# Whether the attachment versioning feature is activated or not
xwiki.store.attachment.versioning=0
#-# Whether the attachments should also be rolled back when a document is
reverted.
xwiki.store.rollbackattachmentwithdocuments=0
It appears that xwiki.cfg setting xwiki.store.attachment.versioning.hint=void
is redundant with xwiki.store.attachment.versioning=0
Question for all: Is the latter the preferable way of turning off attachment
versionining?
Niels
http://nielsmayer.com
PS: doesn't it make sense to avoid such problems in the future and bypass
the recycle bin for deleted attachments. Alternately, some kind of heuristic
could be employed, as the default, e.g. the recylcle-bin is used to hold
deleted attachments, except when the attachments exceed a certain size, say
1Mb. In that case the user is warned of permanent deletion and can "ok" it
away.