Adam Cooper

Just wanted to chime in here that there is an active Rails 3 fork that I've been maintaining and pulled in several of the outstanding changes in forks including the...

In fact, I have dealt with paperclip and vestal_versions on my project. I've posted up the relevant parts here: https://gist.github.com/667933 Let me know if you have any questions. Cheers, Adam

We are using this plugin and planning to maintain our fork of it and we've been pretty active on trying to keep it up to date and adding new features....

Hehe. It's not any more hacky than the other fixes. ;) I ended up pulling in another branch though because it seemed less intrusive. Mostly, it didn't require a schema...

Hi, You can inspect the versions record directly. Here is an example: ``` u = User.create(:name => 'test') u.update_attributes(:name => 'jim') u.versions.first.modifications => {"name"=>["test", "jim"]} ``` I believe the 'modifications'...

I've been looking through the source and was wondering the same thing? Especially now that there is a the rich ActiveSupport::Concern in ActiveSupport 3.

Here is a minimal repository with a reproduction of the issue with rails, guard, sentry: https://github.com/adamcooper/sentry_guard_bug There are steps in the readme on how to reproduce the issue. Let me...

@mixonic - Yes. Having an option to also update the `updated_at` during the `update_all` calls is exactly what I'm looking for. I had my terminology mixed up with `rearranging` vs....

@mixonic - I was thinking along the lines of something like this: https://github.com/zozi/ranked-model/commit/62a743b8398e49a16ac46193a0155c0558bc4ba6

We are having the same issue. Also would be interested in a fork that doesn't have this deprecation warning.