Yes, confirmed--- that was the problem, I didn't (/realize I had to) set the MIME type for mobile in config/initializers/mime_types.rb
if the error message could say something like "You need to register the mime type to use for format for :mobile in config/initializers/mime_types.rb" that would be much more helpful. It makes perfect sense, I just didn't realize I had to do that. Thanks On May 22, 2011, at 2:37 PM, Michael Koziarski wrote: >> I posted this to the Rails Talk list but no one responded. I'm not >> exactly sure what "rails core" is defined as -- this problem is deep >> inside activesupport, can be reproduced in seconds on a fresh new >> Rails app, and I think setting the format request seems pretty "core" >> to the platform to me, so I'm still not sure if this is the right list >> but it seem like this is in fact a Rails core problem. > > The error message you're receiving is pretty confusing, so there's > definitely something nicer we should do there. However I'm guessing > that this isn't a bug. > > You have to register a mime type for that extension, or an alias, if > you want it to work. Something like: > > Mime::Type.register_alias "text/html", :mobile > > If you don't, then rails can't tell what mime type to send with the response. > > > -- > Cheers > > Koz > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" 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-core?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core?hl=en.
