similar to: AuditTrail in Rails

Greetings! I''m attempting to use the act_as_versioned plugin to provide versioning functionality for my rails app, but can''t think my way through this: How can you use act_as_versioned to perform versioning on a HABTM join table? It is easy to see how to do so for join models (:has_many :through) but not so for the join table. I want to use act_as_versioned to maintain

Building on the great ''acts_as_versioned'' plugin by technoweenie, I''ve written a small plugin which also stores versions of associations. It''s early and experimental at the moment, but does work. For example: class Article < ActiveRecord::Base has_many :images has_and_belongs_to_many :categories acts_as_versioned acts_as_versioned_association

Hello, I have been looking for documentation for acts_as_versioned_association and can''t really find any. I have acts_as_versioned_working properly but want to change to acts_as_versioned_association. Do I need to create a 3rd table to use as a reference or is it all done behind the scenes and all I need to do is add the plug-in and: acts_as_versioned acts_as_versioned_association :

I''ve installed the acts_as_versioned gem, and it shows up as installed when i do a "gem list" After installing it, I set up my new model with the "acts_as_versioned" line in its model file. I think went to run my migration to create this table, and I got the following error: == CreateDpslevels: migrating ================================================ --

has anyone has any idea how to implement audit trail table for all update / deletion done on records? I''m thinking to have corresponding audit trail table to each table, so everthing before an update or deletion is done, a new record will be insert into the corresponding audit trail table. Is there a way to overwrite the save, destroy, method at the application level? so that I do not

Hi, I am having trouble with using the acts_as_versioned plugin. I installed the plugin, and ran the migration. acts_as_versioned created the versioned table OK, but when I try to use it I get an error. Here is some console output: >> m = Mymodel.find(:first) NameError: undefined local variable or method `acts_as_versioned'' for Mymodel:Class Did I miss a step? Ingo --

I am looking at using acts_as_versioned to manage revisions of data in several tables in my application. However, the default behavior of acts_as_versioned appears to apply to individual rows within a table. The tables I want to version are complicated lookup tables and what I really want is to version the entire contents of each table as a single set. Adding a row, deleting a row, or updating

Hi all, Despite switching to mod_fcgid (which has improved performance), sessions are still expiring sporadically. I thought I might try switching to storing them in the db, but I get the following error when I try to run the rake create_sessions_table command D:\User\Code\ruby\prometheus>rake create_sessions_table (in D:/User/Code/ruby/prometheus) rake aborted! undefined local variable or

Hi All, Rails newbie here trying to set up acts_as_versioned according to Chapter 14 in the Rails Recipies book. I''ve taken the following steps (nearly verbatim) as mentioned by the book: - created the target model "Post" - added the "acts_as_versioned" label to the model file - generated a migration file - added the table creation code and the command

Hey guys and gals, I have the following object that has acts_as_versioned: class Note < ActiveRecord::Base acts_as_versioned belongs_to :user end The schema for my notes table is as follows: create_table :notes, :force => true do |t| t.column :id, :integer t.column :noteshare_id, :integer t.column :user_id, :integer t.column :title, :string

Hi list, I''ve got some counter_caches in a model. When these get incremented - say on a page view - my updated_on column also gets updated. How can I conditionally not update updated_on if just these counter_cache columns change? The problem with that is that I am using acts_as_versioned which clones the record each time updated_on changes. I am successfully ignoring the counter_cache

I am looking at using acts_as_versioned to manage revisions of data in several tables in my application. However, the default behavior of acts_as_versioned appears to apply to individual rows within a table. The tables I want to version are complicated lookup tables and what I really want is to version the entire contents of each table as a single set. Adding a row, deleting a row, or updating

Hi people I have tried to install the acts_as_versioned gem from github in rails 2.2.2 but it seems to conflict with some methods in the activerecords dirty.rb-file. I can solve some of the problem by changing code in the activerecord, but I don''t think that was the intention. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to

I am trying to use acts_as_versioned and acts_as_taggable (plugin) on the exact same model. Has anyone successfuly done this? I think what I need to do is make model_versions acts_as_taggable instead of my main model. Anyone have any other suggestions or any suggestions how to do this? Your Friend, John Kopanas http://www.kopanas.com

Hi there, This always used to work for me... but not now. I want to blame Rails 1.2 but I''m sure its not. I can''t use AR models in my migrations. To make sure its not just my dodgy code I tried to do the same with a well known plugin.. acts_as_versioned. A migration such as the one below (taken from acts_as_versioned) is giving the error undefined method

Hi, I'm integrating acts_as_versioned (ar-versioned.rubyforge.org) in my customized CMS rails application to set up revision control for pages. Getting and viewing versions works allright, but when I try to revert to a version in the following way, nothing happens to the actual data in the object. Link from page: <%= link_to image_tag('revert'), :action => 'do_revert',

I''m working on a simple product catalog. Products have user defined attributes, such as: color, size, weight. More attributes can be added at any time. Since these attributes are not known ahead of time, they cannot be created as columns. My table structure (simplified): products -------- id name attrs -------- id name product_attrs -------- id attr_id value And some sample code: ##

Hi, I seem to remember seeing the equivalent of saving only if all attributes are different. I can''t seem to find that now in the API or the agile book. I''m using the acts_as_versioned and only want to save if the input is different. Thanks, Steve http://www.smarkets.net -------------- next part -------------- An HTML attachment was scrubbed... URL:

The subject says it all: Has anyone had any experience with using globalize and acts_as_versioned (or equivalent) together. That is, I would like the version control to take the locales into account, the en-US translation could be on version 7 while the fr-FR version is 3. Am thinking about extending these plugins but maybe someone has already done this? Tanks in advance. Regards Erik Lindblad

Hello all, while I''m using acts_as_audited(on jruby platform), after vendored the acts_as_audited, it reports some error, line 167, # Start observing the declared classes and their subclasses. def initialize Set.new(observed_classes + observed_subclasses).each { |klass| add_observer! klass } #this line end after some trace shows this one, when observed_classes is empty, will