This is one of those errors in Rails that just make you go WTF!? The amount of debug information is minimal, and the row that supposedly is the culprit is syntactically correct. Even Google doesn’t really help. I gather that this error can occur in several different contexts and caused by different things, so I’m not trying to provide an all purpose solution to this. The case I’m going to show you is probably quite rare, but it happened to us at work today. I never figured out exactly why Rails chokes in this situation, but I found a way to reproduce the problem and also a solution. The main characters in this drama are the respond_to and render methods, and the main villain is a mysterious invisible parameter.
Blogroll
My sites
Categories
Archives
- March 2010 (3)
- January 2010 (1)
- December 2009 (12)
- June 2009 (1)
- May 2009 (1)
- April 2009 (2)
- January 2009 (3)
- October 2008 (1)
- September 2008 (1)
- August 2008 (4)
- July 2008 (1)
- June 2008 (4)
- May 2008 (3)
- March 2008 (2)
- February 2008 (1)
- January 2008 (6)
- December 2007 (6)
- October 2007 (2)
- August 2007 (3)
- July 2007 (2)
- June 2007 (2)
- May 2007 (1)
- April 2007 (7)
- March 2007 (1)
- November 2006 (1)
- October 2006 (2)
- August 2006 (5)
- July 2006 (4)
- June 2006 (4)
- May 2006 (1)
- April 2006 (9)
- March 2006 (2)