Version history for models

[Grant McLean]

Hi Railers

I'd like to track a history of updates to records in selected tables.
The aim is to provide an audit trail of who changed what and possibly
the ability to revert selected changes.

A bit of googling brought me to the "Vestal Versions" plugin:

https://github.com/laserlemon/vestal_versions

Does anyone have any experience with this or other related plugins?
Good bad or otherwise.

It looks like I'm going to have to do a Rails upgrade before I take
anything for a test drive.

Cheers
Grant

[Nahum Wild]

There is also this:

https://github.com/collectiveidea/acts_as_audited

Which I've never used :-)

--nahum

Grant

--
You received this message because you are subscribed to the Google Groups "WellRailed" group.
To post to this group, send email to wellr...@googlegroups.com.
To unsubscribe from this group, send email to wellrailed+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/wellrailed?hl=en.

[Warren Seen]

We've used paper trail at codefire and found it to be simple and reliable for our needs: https://github.com/airblade/paper_trail

[Henry Collingridge]

We've used acts_as_audited and it did what it says on the tin.

[Cameron Prebble]

+1 on Paper trail 

You might also find this page helpful

https://www.ruby-toolbox.com/categories/Active_Record_Versioning

Grant

--
You received this message because you are subscribed to the Google Groups "WellRailed" group.
To post to this group, send email to wellr...@googlegroups.com.
To unsubscribe from this group, send email to wellrailed+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/wellrailed?hl=en.

--
Cameron Prebble

Phone: 021 174 1296

http://cameron-prebble.com | http://mashblock.co.nz | http://quakemap.co.nz

[Shane Mingins]

I have on two projects and it's been ok.  The main worked needed was in presenting the information back to the users in a nice way.

--
Shane Mingins

[Nahum Wild]

good to know it's worked fine. presentation of the audit data is always gonna be a problem...

--nahum

[Darryl Hamilton]

Hi Grant

Paper Trail (https://github.com/airblade/paper_trail) is another option for tracking update history.

I've only used both to a small extent, so I can't really offer much advice on suitability.

Darryl

On Wed, Feb 8, 2012 at 4:28 PM, Grant McLean <gr...@catalyst.net.nz> wrote:

Grant

[Gordon King]

+1 for paper trail. I trialled vestal versions and paper trail and found it clean and simple. Saves the whole record and not just the diff like vestal. Rails 3 gem gives you some nice methods for getting at the diffs.

I recommend htmldiff gem for iterating the object versions and displaying the audit trail.

[Gordon King]

[Gordon King]

Oh and avoid the active record diff method suggested for paper trail. It breaks in rails 3.2