Excerpts from Leonardo Mateo's message of Tue Feb 22 17:12:06 -0800 2011:
> Excerpts from Phil Crissman's message of Sun Feb 20 15:14:45 -0800 2011:
>> > Started POST "/items/28/price" for 127.0.0.1 at 2011-02-20 18:52:10 -0300
>> > ActionController::RoutingError (No route matches "/items/28/price"):
>> First check: is this route listed when you do `rake routes | grep price` ?
> Second check: Confirm that your form really does have method=POST.
Yes, it does. Anyway, I've just changed it to use the update action,
it makes more sense anyway.
However, I still don't understand why it is happening.
Something I should have been more clear about: you want to make sure that your
form element has its method attribute set to post, but you will also need to
check that it does not have a hidden parameter generated by rails named _method
with a value of, e.g. put.
Unfortunately when you make this mistake of specifying a post route in
config/routes but accidentally submitting to a synthetic "put" (very easy to do
if using +form_for+), the log will still read “Started POST” and you will be
given no indication of the problem.