This project is archived and is in readonly mode.

#5032 open

accepts_nested_attributes_for not working more than one level deep?

Reported by scrozier | July 2nd, 2010 @ 01:21 AM

This is a bit preliminary, but since it is related to a recently resolved ticket (2415), I thought it worth reporting.

After installing 2-3-stable today, my one-level-deep nested attributes are now updating correctly, but I am still seeing a problem when there is more than one level of nesting. In that case, it is looking like the "grandchildren" records are only updated if at least one attribute changes in the related "child" record. Otherwise, no update is done on the grandchildren.

It's quite possible that this is my problem...anyone else?

Working on a test case....

Comments and changes to this ticket

  • scrozier

    scrozier July 2nd, 2010 @ 06:10 AM

    A little more info:

    I can consistently reproduce this in my application.

    I can "fix" this by making the changed? method in module Dirty return true if self.class == Child. Making the condition self.class == Grandchild does not work.

    I am trying to backtrace this to a higher level call....

  • scrozier

    scrozier July 2nd, 2010 @ 11:12 PM

    Forcing a change to Child also make grandchildren update correctly, as expected.

  • Jeff Kreeftmeijer

    Jeff Kreeftmeijer November 8th, 2010 @ 08:27 AM

    • Tag cleared.
    • Importance changed from “” to “Low”

    Automatic cleanup of spam.

  • Santiago Pastorino

    Santiago Pastorino February 9th, 2011 @ 12:31 AM

    • State changed from “new” to “open”

    This issue has been automatically marked as stale because it has not been commented on for at least three months.

    The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

    Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

  • Santiago Pastorino

    Santiago Pastorino February 9th, 2011 @ 12:31 AM

    • State changed from “open” to “stale”
  • Ingo Wichmann

    Ingo Wichmann March 18th, 2011 @ 02:53 PM

    Using rails 2.3.11 I can confirm this bug

  • Daniel

    Daniel March 18th, 2011 @ 06:51 PM

    • State changed from “stale” to “open”

    [state:open] I also still see this problem in 2.3.11.

  • af001

    af001 May 5th, 2011 @ 02:54 AM


Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2 style="font-size: 14px">Tickets have moved to Github</h2>

The new ticket tracker is available at <a href=""></a>