collectiveidea / acts_as_audited

if i put "acts_as_audit" in a model it try to audit the changes, but the sweeper is not called. So i ever need to "audit Model" in the controller.

I declare in my application.rb:

audit User, PaymentAccount, Client, Product, Price, Contract, AssignedAdsl, ContractPrice, Role

But in production, only User, Client, Price and AssignedAdsl are audited. In development, all models are audited.

It's weird, but it's true. Does anybody know what might cause this?

When there are two separate controllers that audit a model, there are duplicate audits created when class caching is enabled. For example:

class PostsController < ApplicationController
  audit Post, :only => :create
  ...
end

class AdminController < ApplicationController
  audit Post
  ...
end

Testing with Rails 2.3.3 on Ruby 1.9 fails.

I'll be making sure it works on 1.8.6, 1.8.7 and 1.9.1 over the next few days. Any work in progress will be on my fork, in the collectiveidea branch.

http://github.com/kennethkalmer/acts_as_audited/tree/collectiveidea

I have audits table on a local (to rails) server and the rest of tables are located on a remote server.
I get "NoMethodError (undefined method `controller_name' for nil:NilClass)" every time I try to save or delete any record. I'm using :only => [...] param, because otherwise I get that error on every request to any resource.

Removing audit from the application controller stops the error message to appear.

In my application controller I have something like
audit Model1, Model2, Model3, :only => [:update, :destroy]
However, all three actions are being audited.
Looking at the code it appears that the :only option is treated in two different ways. In the acts_as_audited method, :only is used to modify the attribute list (not the actions). However in the controller/sweepers creation audit method, the :only option (and any others) is passed on to the sweepers. So, I'm not sure which way you intended this to go. It feels a little odd to have :only and :except do two totally different things, so would another option (:action?) be in order? Any other ideas or am I reading this wrong?
Rails 2.3.2
Thanks for your help!