Skip to content
Browse files

Add note about upgrading custom routes from `put` to `patch`.

  • Loading branch information...
1 parent 432ffdb commit 03dbd8af56c8c45f8b39aa6e081656bd13c06c4a @javan javan committed May 24, 2013
Showing with 18 additions and 0 deletions.
  1. +18 −0 guides/source/upgrading_ruby_on_rails.md
18 guides/source/upgrading_ruby_on_rails.md
@@ -41,6 +41,24 @@ So, in Rails 4 both `PUT` and `PATCH` are routed to update. We recommend
switching to `PATCH` as part of your upgrade process if possible, as it's more
likely what you want.
+Note, when using `form_for` to update a resource in conjunction with a custom route,
+you'll need to update your route to explicity match the `patch` verb:
+
+```erb
+<%= form_for [ :update_name, @user ] do |f| %>
+ ...
+<% end %>
+```
+
+```ruby
+resources :users do
+ # Rails 3
+ put :update_name, on: :member
+ # Rails 4
+ patch :update_name, on: :member
+end
+```
+
For more on PATCH and why this change was made, see [this post](http://weblog.rubyonrails.org/2012/2/25/edge-rails-patch-is-the-new-primary-http-method-for-updates/)
on the Rails blog.

0 comments on commit 03dbd8a

Please sign in to comment.
Something went wrong with that request. Please try again.