This project is archived and is in readonly mode.

form_for for singular resource will products plural invokes

#267

for example:

in routes.rb

   map.resource :profile, :controller => 'profile'

in view:

   <% form_for(@profile) do |f| %>
      ...
      <%= f.submit "Save" %>
   <% end %>

if @profile.new_record? is true, it will raises a NoMethodError exception with the message:

undefined method `profiles_path' for #

if @profile.new_record? is false, the message is

You have a nil object when you didn't expect it!   The error occurred while evaluating nil.to_sym

confirmed on

ruby: ruby 1.8.6 (2007-03-13 patchlevel 0) [i686-linux]

rails: freezed revision 9084

and

ruby: ruby 1.8.6 (2007-03-13 patchlevel 0) [i386-mswin32]

rails: rails 2.0.2

Reported by soliiid · July 17th, 2008 @ 02:01 AM

Activity

josh
- State changed from new to stale
- Tag set to actionpack, helper
Interesting. Unit tests please.

July 17th, 2008 @ 02:03 AM
Andrew White
Looks like there's a couple of problems relating to singular resources here:
1. When the object is a new record the inflection passed to the build_named_route_call in polymorphic_url is :plural instead of :singular
2. The object is passed to the named route call which it isn't expecting resulting in the nil.to_sym exception
The question is how to fix it? A quick workaround is to specify the url in the form_for call e.g:
<% form_for(@profile, :url => profile_path) do |form| %>
A proper fix is a little bit more tricky as polymorphic_url on the face of it can't know whether the object maps to a singular resource or not

July 28th, 2008 @ 12:22 PM
Jérôme
Any good news about this error ? :(

October 4th, 2008 @ 11:04 AM
mike
bump

December 16th, 2008 @ 10:27 PM
Adam S
I would like to see this fixed as well... Workaround here: http://www.expressionlab.com/200...

January 18th, 2009 @ 01:35 AM
Claudio Poli
just bashed my head 30 mins on this.

June 2nd, 2009 @ 10:32 AM
Gravis
+1 for this bug :)

the result is pretty unexpected

September 17th, 2009 @ 11:09 AM
AI
I ran into this bug today. The obvious workaround is to define singulars_path as singular_path in SingularsHelper, but a real fix would be nice.

December 9th, 2009 @ 11:13 PM
jd
+1 :) Hi. Same issue for me using Rails3 beta.
Also, although I'm not sure it would not be a design flaw, one may like to have app/views/resource instead of app/views/resources in the case of a singular resource... ?

March 12th, 2010 @ 03:46 AM
Pete
+1...i'm having this issue in rails 2.3.5

March 14th, 2010 @ 10:37 PM
Brendan Loudermilk
+1 on this two year-old bug

June 1st, 2010 @ 10:40 AM
eagle.anton (at gmail)
- Tag changed from actionpack, helper to rails 3 rc, actionpack, helper
- Importance changed from to
Confirm bug in Rails 3 RC

July 29th, 2010 @ 08:19 AM
Ellis Berner
+1

October 14th, 2010 @ 07:04 PM
Jake Moffatt
+1

February 24th, 2011 @ 11:30 PM
Victor Costan
+1

February 28th, 2011 @ 12:34 AM
Eric Hahn
+1

Two gotchas with singular resources:

1) you have to force the :controller to the singular in the route (or have your singular resource be served by a plural controller)

2) you have to explicitly provide the :url to the singular path in form_for, etc.

March 24th, 2011 @ 09:39 PM