similar to: Active Record Observers causing 404''s and other weird issues

Hi all, I''m developing a site where a user can upload their CV/resume with a profile, and am using restful_authentication for this with attachment_fu to handle the file uploading. When a user creates their profile/user account, I''ve got an observer that will email the site admin with a copy of the uploaded CV. My user_observer looks something like: class UserObserver <

Help please. I''m trying to observe a User class, but I can''t get this to work, the after_create method never gets called... (the breakpoint never gets called) app/models/user_observer.rb: class UserObserver < ActiveRecord::Observer def after_create(user) breakpoint setting =

Hi all ! I''m having an issue and I can''t seem to make heads or tails of it. I am attempting to add an observer to a model object. I created app/models/greenback_transaction_observer.rb, inherited from AR::Observer, defined methods, registered in config/environment.rb, but things don''t work... So, I took a step back and put in the following code: class

eh, like so? def after_create(model) generate_hotel_param_files(model.id) generate_hotel_setup_files(model.id) end def after_update(model) generate_hotel_param_files(model.id) generate_hotel_setup_files(model.id) end On Jul 21, 9:59 am, David Nguyen <rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org> wrote: > Hi, > I have to make an observer if a

Hi all, I have a problem with an observer. I have a simple observer... class ActivityObserver < ActiveRecord::Observer observe Customer def after_create(model) bind_params(model) @al.action = "create" @al.save logger "#{model.id} : created" end private def bind_params(model) @al = ActivityLog.new @al.user_id = User.current.id

i followed the observer documentation [1] and created, and registered an observer. i had to realise that the observer doesn''t work at all -- in fact the rails application does not even start -- with acts_as_taggable, for whatever reason. i must admit that i''m still using ruby 1.8.2. however, after commenting the acts_as_taggable instruction out the application runs smoothly

I was just wondering what about a report that I made almost 2 months ago: Active Record observers broken<https://rails.lighthouseapp.com/projects/8994/tickets/4087-activerecord-observers-cant-be-used-for-before-callbacks> I think it''s a pretty big bug. In Rails 3, creating an observer with a "before_save" callback (for instance) will result in all observed models being

Switchboard is a simple, event-observing framework for ActiveRecord. It''s designed to make it easy to add observers for all models in your app, and to easily turn them on and off selectively. Intallation gem sources -a http://gems.github.com sudo gem install zilkey-switchboard Usage First, require switchboard above your rails initializer: # environment.rb require

Hello I''m using the ''act_as_authenticated'' plugin to implement a small and simple authentication system in my app. Everything is working just fine and the world is a better place to live in. The plugin creates a ActiveRecord observer in order to send the newly registered user a confirmation e-mail. Per the API docs [1], one should declare the observer in the

I''ve seen two ways of connecting observers: 1) In the observer class put observe MyModel 2) In the controller class put observer :my_observer What is the difference between these two? Also, is it necessary to put in the observer class the following? MyObserver.instance Jose -- Posted via http://www.ruby-forum.com/.

I''m pleased to announce the existence of async-observer. This is the very first public release. In the future I''ll confine announcements to the beanstalk-talk mailing list. WHAT IS ASYNC OBSERVER? ----------------------- Async Observer is a Rails plugin that provides deep integration with Beanstalk. beanstalkd is a fast, distributed, in-memory work-queue service. Its

I need to add an ActiveRecord observer and thought I should follow Rails 2 intent by not changing the base environment.rb I create a file config/initializers/observers.rb but don''t know what to add to it. I can''t add: config.active_record.observers = :user_observer Since "config" isn''t defined in the scope of the initializer file and I don''t know if

I''m not sure how to implement this so I''ll describe what I currently have done then what I wish to have happen currently, I have a generic observer for several models class AuditObserver < ActiveRecord::Observer observe Foo, Bar def after_update(model) model.log("UPDATED " + Time.now.strftime("%m-%d-%Y %H:%M")) end def after_create(model)

Greetings all, As a Noob, I''ve been diligently working my way through the AWD4R book and finally arrived at the part about observers -- which BTW I think are very cool tech. Anyhow, I got the Audit Observer working. Now I want to test it and perhaps examine it''s attributes and methods to make sure it does what is expected of it. For example, one thing I would like to do

Hi, I''m developing a Rails app which uses dynamic forms. To implement these, I''ve used AJAX and Rails''s built-in form observers. Unfortunately, I''m having a problem. This is how the form starts: * Country select box [OBSERVED] (Republic of Ireland selected) * County select box [OBSERVED] (none selected, list of Republic of Irish counties in the drop down)

I haven''t seen it documented anywhere, but can observer methods be given a prefix in their name like ''after_'' followed by my controller''s method name? For instance I have a couple of methods called ''create'' and ''create_reply''. Can I have ''after_create'' and ''after_create_reply'' in my

Hello all! I''m having an issue with Observers, and I''m hoping someone knows the answer. Here is the definition: app/models/vehicle_observer.rb > class VehicleObserver < ActiveRecord::Observer > def after_save(vehicle) > breakpoint > if vehicle.has_new_mil_indication? > UserMailer.deliver_mil_notice(vehicle) > end > end > end

I''m spec''ing a model with an observer that sends mail. Mailers behave similarly to controllers, so to make the whole thing work, I believe something like integrate_views has to be available. Has anyone dealt with observers and ActionMailer? Thanks

Hello, I''m a newbie to aaf and rails and I hope anyone can help me with this. I have the following Models: class Project < ActiveRecord::Base acts_as_authorizable acts_as_audited :except => [:created_by, :updated_by ], :user_class_name => ''AuthenticatedSystem'', :user_method => ''current_user'' acts_as_ferret :fields => {:name =>

Observers will be no more as of Rails 4, farewell, never been much of a fan. However, I''m using it in one of my gems which enables model attributes for use with a WYSIWYM editor. The resulting markup is persisted, but in order to use it in a view, it has to be nokogiried in a helper which fragment caches the result. This cache has to be zapped once the model instance is either