Forum: Ruby on Rails acts_as_versioned with acts_as_paranoid not creating new ver

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
11364e09c2ea04444314e94eead06e98?d=identicon&s=25 Roland Swingler (Guest)
on 2007-04-04 15:02
(Received via mailing list)

A quick question, when using acts_as_paranoid with acts_as_versioned,
destroying the model (i.e. updating the deleted_at field) doesn't
create a new version. Are there any workarounds for this - I presume
it is because aav overrides the update* methods but not the destroy

In addition, and more confusingly, using the before_destroy callback
like so:

def before_destroy
  update_attributes(:some_field => 'some value')

doesn't create a new version, even though an update is being done. If
you do an update_attributes in the controller then it does create a
new version, as expected. This confuses me slightly - why would
*where* you are calling the update_attributes method from make a

Any help with this appreciated,

This topic is locked and can not be replied to.