similar to: after_create not creating the right object

Imagine I want to track people, and the clubs that they belong to. table people with columns person_id, person_name table clubs with columns club_id, club_name And I have the association table: table clubs_people with columns person_id, club_id Now I know how to do this habtm between the two, in order to associate people with clubs that they belong to. However my application also needs a

A friend and I are just in the process of trying to create PDFs on the fly. This isn''t in itself too hard, but we have some repeating images that are being put in over and over again. It''s increasing file size too much unfortunately. Does anyone know the best way to ensure file size is kept to a minimum for this scenario? We know about linking to a URI, but the problem with

Hello, I''ve come across an issue that I''m sure is a bug when using after_create with a has_one association, but I''m not 100% certain if I''m missing something. This is pretty much exactly the code I''m using. Two simple classes (Account and Contact) and I create the contact after I create an account (via after_create). I''m not passing in a

Hi, AFAIK after_create is called after_save if the entry does not exist in the DB. Is there a way to tell if a specific model is new or not in after_save? I have to do something like: def after_save add_to_history ''save'' end def after_create add_to_history ''create'' end However after_save is called when creating too. -- cheers, M.

Hi all I have the following model: class PhotoGallery < ActiveRecord::Base attr_accessible :title, :description, :file_path, :title_photo_id has_many :photos, :dependent => :destroy belongs_to :title_photo, :class_name => ''Photo'', :foreign_key => ''title_photo_id'' validates_presence_of :title, :description, :file_path

I have a User model with a protected method defined: def set_role(rolename) role = Role.find_by_rolename(rolename) permission = Permission.new permission.role = role permission.user = self permission.save(false) end and a subclass with: after_create set_role(''client'') This always fails for me with the error: undefined method `set_role''

I don''t get what class Test is for, or where the registration model is, but remember that registrationS is the collection object. I think you want something like after_create { self.registrations << Registration.new } Cheers, B Gates I want to automatically create a registration entry when I add a new user to my application. This works fine, but it''s not

Hi, I realized the order of the after_create callback is dependent on where in the class it is defined. I wrote a blog post about it, but am not sure where in the code one might begin to resolve this issue. I''m hoping someone else might be able to help out or guide me in the right direction: http://ablogaboutcode.com/2011/08/17/after_create-bug-in-rails-3/ Thanks, Pan -- You

Hi, I think I''m missing some fundamental information here so hopefully someone can help me. I have a model Club which has many members, members of course belong to a Club. I''d like to ensure that when a members is saved (saved/created/updated) only valid club_id''s are accepted. I have a Club model (simplified) like this: class Club < ActiveRecord::Base

All, I''ve been trying to figure out a strange bug in one of my applications that I think I''ve narrowed down to a problem with rails fixtures. It seems as though the after_create callback is being run twice when I save a record. This is only happening a) in the test environment, and b) when there is a fixture file for that table. The test below only prints "Doing

Hi, I am trying to get into this REST thing, I have a nested resource whith the following route: ActionController::Routing::Routes.draw do |map| map.resources :members map.resources :clubs do |club| club.resources :members end map.connect '':controller/:action/:id'' map.connect '':controller/:action/:id.:format'' end Everything worked ok for this

Hi all. I am actually using ActiveRecord outside of Rails but I don''t see that it matters for this question. I want to automatically create a registration entry when I add a new user to my application. This works fine, but it''s not automatic: class User < ActiveRecord :: Base has_many :registrations end class Test user = User.new user.registrations.create end

Hi all I''m moving to using Machinist in my rspec tests and am having a problem with an after_create callback method that i need to stub out. It seems like calling ClassName.make will trigger this callback before i''ve had the chance to stub it. Can i stub it in my blueprint for that class? Or, can i stub the method for all instances of the class before i call ClassName.make?

How to update attribute(s) and save a record instance without triggering the hooks: after_save, after_create, after_update? I know it''s possible with Record.update() but this is dynamic. Only receive the instance, without knowing its class (thus cannot call the class method update()). Or is there a way of knowing the class and calling the class method? Thank you. -- Posted via

Scenario: I''m creating an image file upload service for my web site. As well as saving the actual file I also need to create a database record for the file. I would like to name the file after the record id, but I also need to save some attributes of the image (width/height/mime_type etc) which I can''t discover until after the file is created. The Problem: 1) The id is not

I''ve written a story and I run into a snag. I''ve written the create_forum method and told it to set the id to 1 but when it creates the forum the id is autoincremented. My forums table is empty but the id keeps incrementing the newest record on creation. When I run the story it comes out as something like 59 which fails my story because I''m asking it to look at /forums/1

Hi, This is just kindof a RoR question, but since you all potentially do the same things as I do, I thought I''ll ask here.. Im trying to use the boolean type in the database. Migrations is no problem, it even converts the 0/1 values from my import CSV to false and true. However, I cannot make the :conditions part of a find work: Loading development environment (Rails 2.0.2) >> c

I''ve got a model Message, which needs to send an email using action mailer after it''s first saved in the database. I want to pass the model to the mailer which then uses methods on the message model to render the email. So the natural way to do this is in an after_create callback on the Message model. But I can''t see an easy way to test this. Here''s my spec

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

I wrote this abomination just now, and wonder if anyone else has had experience with the pattern behind it. In short, I''m specing an after_create hook on an ActiveRecord model, that calls a bunch of private methods. Instead of stubbing all those private methods (which is verboten anyway, as well as impossible because creating the object which owns those methods is what I''m