# Acts\_as\_versioned with acts\_as\_paranoid not creating new ver

**URL:** <https://www.ruby-forum.com/t/acts-as-versioned-with-acts-as-paranoid-not-creating-new-ver/91082>\
**Category:** Rails\
**Created:** [April 4, 2007, 3:02pm UTC](https://www.ruby-forum.com/t/acts-as-versioned-with-acts-as-paranoid-not-creating-new-ver/91082 "2007-04-04T15:02:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![schmitr3](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ea666f/32.png) [@schmitr3](https://www.ruby-forum.com/u/schmitr3)\
**Post date:** [April 4, 2007, 3:02pm UTC](https://www.ruby-forum.com/t/acts-as-versioned-with-acts-as-paranoid-not-creating-new-ver/91082/1 "2007-04-04T15:02:12Z")

</div>

Hi,

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  
method?

In addition, and more confusingly, using the before\_destroy callback  
like so:

def before\_destroy  
update\_attributes(:some\_field =\> ‘some value’)  
end

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  
difference?

Any help with this appreciated,

TIA,  
Roland