So far I have only tested this with COREBlog2 and
EasyBlog. But if you set the edit policy to Create
version on edit for their respective entry types, the
version are not created when edits are made.
For EasyBlog, the problem is that they use the same
method that CMFEditions uses to install
update_version_on_edit action to install their own
action thus replacing it.
EasyBlog is based on Archetypes, while COREBlog2 uses
ATContentTypes. But since both install their own
validators, they break the means by which
update_version_on_edit is called.
Question: Is there a better way to enable this
capability that is not as easily broken should a
product provide its own action to be called by
validate_integrity upon success?