nested-attributes

I two models User and Submission as follows: class User < ActiveRecord::Base # Associations has_many :submissions accepts_nested_attributes_for :submissions # Setup accessible (or protected) attributes for your model attr_accessible :email, :name, :role, :submission_ids, :quotation_ids, :submissions_attributes validates :email, :presence => {:message => "Please enter a valid email address" } validates :email, :uniqueness => { :case_sensitive => false } end class Submission < ActiveRecord::Base belongs_to :user attr_accessible :due_date, :text, :title, :word_count, :work_type, :rush, :user,

My environment: Rails 3.2 with draper gem I'm using nested resources and having trouble figuring out where to declare the decorator. #app/controllers/users_controller.rb def show @user = UserDecorator.find(params[:id]) @items = @user.items end #app/controllers/items_controller.rb def show @item = @user.items.find(params[:id]) end I tried replacing items with ItemDecorator and it didn't work. Where should I be putting it? I know that Draper has issues with nested resources in forms, but this isn't a form! As far as I've understood your problem correctly, you've a model user which has many items

Im trying to create two hidden fields, and one shows up no problem, but the other that comes from the nested form does not product.rb class Product < ActiveRecord::Base has_many :product_options, dependent: :destroy accepts_nested_attributes_for :product_options, allow_destroy: true, :reject_if => proc { |x| x[:option_name].blank? } belongs_to :user end product_option.rb class ProductOption < ActiveRecord::Base belongs_to :product end products_controller.rb class ProductsController < ActionController::Base layout "application" def index @products = Product.all @current_user = Client.find_by(id

My problem is I've run into limitations of accepts_nested_attributes_for, so I need to figure out how to replicate that functionality on my own in order to have more flexibility. (See below for exactly what's hanging me up.) So my question is: What should my form, controller and models look like if I want to mimmic and augment accepts_nested_attributes_for? The real trick is I need to be able to update both existing AND new models with existing associations/attributes. I'm building an app that uses nested forms. I initially used this RailsCast as a blueprint (leveraging accepts_nested

Issue: Instead of updating nested attributes, they are being created on top of the existing nested attributes when I hit the #update action of the associated features_controller.rb Likely Cause: I think the problem lies in my lack of understanding in Rails' form_for . I think the breakdown is in my views, how I render the persisting nested attributes, and/or how I fail to specify the nested attribute's id, causing it to simply create a new one feature.rb class Feature < ActiveRecord::Base ... has_many :scenarios accepts_nested_attributes_for :scenarios, allow_destroy: true, reject_if: :all

I'm relatively new to rails and finally found the right way to use accepts_nested_attributes_for . However, there are some serious resources on the web who say that using accepts_nested_attributes_for is generally a bad practice (like this one ). What changes are necessary to avoid accepts_nested_attributes_for and in which folder would you put the additional class-file (I guess one needs an additional class). I read that virtus is appropriate for that. Is that right? Here is a very basic example still using accepts_nested_attributes_for (find the full example here ): Models class Person <

I get this error "WARNING: Can't mass-assign protected attributes: races_attributes" , when following this http://railscasts.com/episodes/196-nested-model-form-part-1 on rails 3. Where Races are a component of Events. This is my models/race.rb: class Race < ActiveRecord::Base belongs_to :event attr_accessible :name, :unit end This is my models/event.rb: class Event < ActiveRecord::Base has_many :races, :dependent => :destroy accepts_nested_attributes_for :races attr_accessible :name, :date, :description, :location_name, :address_one, :address_two, :city, :state, :zip, :active, :races