Try adding a hidden field for the user's id in the nested form.
Try adding a hidden field for the user's id in the nested form: The nested save will use this to determine if it is a create or an update for the User.
Rails actually already does this, essentially. If the User object already exists, it adds a hidden bloggeruser_attributesid form field (not present if it's a new user). As the error message in my original notes, Rails knows the ID of the nested model.
– Jase Jun 14 at 21:54 Did you confirm that it's actually showing up in the HTML? – Brian Glick Jun 18 at 17:27 Yes, definitely not a problem with the ID of the nested object being passed. In the error I pasted in original, it knows the ID of the nested object (User) is 7 and the outer object (Blogger) doesn't have an ID yet (because it's brand new).
It just apparently freaks out in that situation. – Jase Jul 6 at 18:43.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.