Given the following:
> = form_for(:photographer, @photographer, :url => resource_path, :html
> => { :multipart => true, :method => :put }) do |f|
> ...
and
> Rails 3.0.0 :
>
> namespace :admin do
> # session / login / logout
> resource :photographer_session
> match '/login' => 'photographer_sessions#new', :as => :login
> match '/logout' => 'photographer_sessions#destroy', :as
> => :logout
> resource :photographer
> resources :photographer_password_resets
> end
Should resource path be something else like admin_photographer_path ? I'm just
guessing, but I'd also look at removing the :photographer and :method => :put
from the form_for line. I think it's import to sort out why your URL is
generating incorrectly before we troubleshoot the content type issue. For
example, it might be thinking that .1 is a suffix just like .html or .css and
is setting the resource type based on that.
Also regarding checking the headers. I'll assume you're using or can use
chrome. Look under the View menu -> Developer -> Developer tools. Click on the
first item under resources (which should say 406) and click on the headers tab.
Here you can find the accept and content type headers.
Luke
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" 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-talk?hl=en.
