similar to: how to use acts_as_versioned_association

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

I''ve spent the weekend giving my acts_as_versioned_association (or version_association for short now!) some much needed attention. Unit tests have gone from a shameful 150 lines to well over 700 now - around 1:3.5 code to test ratio. There''s still probably a lot which needs testing, but it should be a lot better now. It''s a fairly major update and there are some

Hello there, I need to build an audit trail system for an application. So far I have been looking at acts_as_versioned and acts_as_versioned_association plugins. I am having troubles getting the second one to work. Any how, do you have any suggestions about how to build a robust audit trail? Thanks, Roland -- Posted via http://www.ruby-forum.com/.

Anybody using both of these plugins simultaneously? It appears that the methods dynamically generated by rails_file_column don''t get added to the Version class: NoMethodError (undefined method `image='' for #<Opinion::Version:0x35c9254>): .//vendor/rails/activerecord/lib/active_record/base.rb:1847:in `method_missing''

hello, I''m using the trunk versions of both plugins. I''m running into this error when I run a migration to try and create the versioned table for the model ''Note'' stack level too deep /Users/Adam/dev/sweetspot/app/trunk/config/../vendor/plugins/ acts_as_paranoid/init.rb:5:in `belongs_to_without_deleted''

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

Anyone knows how to use namespace with acts_as_versioned-0.5.1? Model example: class Namespace::MyModel < ActiveRecord::Base require ''acts_as_versioned'' acts_as_versioned(:class_name => "Namespace::MyModel", :table_name => my_model_versions'') ... The error looks like: NameError in Namespace::MyModel wrong constant name

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

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

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

Hi, I have Article model and it has aasm_column qa, that is initially "pending". In order to get it reset qa column on new versions, I have made: def set_new_version write_attribute(:qa, "pending") end But now the aasm methods are also triggering the new version, dispite: self.non_versioned_columns << ''updated_at''

Yes, I know about the :if/:if_changed clause on acts_as_versioned ... content_changed or author_changed .... That''s not what I''m asking about. What I''m wondering about is something like applying the spiffy new 2.0 sanitize as a ''before_save'' -- A little inaccuracy can save tons of explanation. -- Saki

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 ================================================ --

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

> However, as I understand acts_as_versioned the models are not synchronized > so when I look up the permissions of an old version of the employee I have > to manually find the corresponding version of the permissions (ie the > version of permissions that existed when that version of employee was > updated), and when navigating to the corresponding system from that > permission I

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

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

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