I may be wrong, but I think rails uses the new_record? method to
decide whether the form should be posted to the create or the update
action when you do something like <% form_for(@dealer) do |f| %>. Are
you sure your transaction is working correctly and that everything has
been rolled back? Can you verify that @dealer.new_record? returns true
after the failed transaction?

On May 19, 6:44 pm, brianp <[email protected]> wrote:
> Yes I have that's how I know it's changing the form method to PUT to
> dealer/id/edit. It's also adding an id of: edit_dealer_id_{#number}
> where {#number} is an actual digit.
>
> On May 19, 9:38 am, Colin Law <[email protected]> wrote:
>
>
>
> > On 19 May 2010 16:44, brianp <[email protected]> wrote:
>
> > > Expecting to get rendered: The same form page I've created at the :new
> > > action with the Invalid model notices from my model validations.
>
> > > What is getting rendered: A form that LOOKS the same, with my Invalid
> > > model notices but now does not POST to the :create action. The form
> > > has magically changed my hard coded input to post to the create action
> > > into a :put method to the :update action.
>
> > Have you checked the html of the page to see exactly what is being
> > generated incorrectly?  View, Page Source or similar in browser.
>
> > > I know it's kind of an obscure problem. Maybe later today I'll post a
> > > git repository with the code needed to recreate the problem.
>
> > > On May 19, 1:13 am, Sharagoz <[email protected]> wrote:
> > >> On May 19, 2:36 am, brianp <[email protected]> wrote:> BUT the 
> > >> page gets rendered as an
> > >> > edit_dealer_id page. with a new hidden field telling the form to
> > >> > submit via put method.
>
> > >> I dont really unserstand what you're saying. What are you expecting to
> > >> get rendered, and what is actually getting rendered?
>
> > >> --
> > >> You received this message because you are subscribed to the Google 
> > >> Groups "Ruby on Rails: Talk" group.
> > >> To post to this group, send email to [email protected].
> > >> To unsubscribe from this group, send email to 
> > >> [email protected].
> > >> For more options, visit this group 
> > >> athttp://groups.google.com/group/rubyonrails-talk?hl=en.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups 
> > > "Ruby on Rails: Talk" group.
> > > To post to this group, send email to [email protected].
> > > To unsubscribe from this group, send email to 
> > > [email protected].
> > > For more options, visit this group 
> > > athttp://groups.google.com/group/rubyonrails-talk?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups 
> > "Ruby on Rails: Talk" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to 
> > [email protected].
> > For more options, visit this group 
> > athttp://groups.google.com/group/rubyonrails-talk?hl=en.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Talk" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to 
> [email protected].
> For more options, visit this group 
> athttp://groups.google.com/group/rubyonrails-talk?hl=en.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en.

Reply via email to