This project is archived and is in readonly mode.
respond_with broke (or fixed) in rails 3.0.3
-
Michael Bensoussan
got the same issue, I'll try to submit a patch if I find some time
-
Dmitry Maksimov
As temporary solution you can pass empty hash as first parameter:
respond_with({}, :location => root_path, :status => :ok)Changes that lead to this error were made by commit d4b7fa5fb6b4aee8dee90b526c08c0dd2e5e97d3.
-
rails
- Tag changed from 3.0.1, 3.0.3, controllers, responders, respond_with to 301, 303, controllers, responders, respond_with
- State changed from new to open
This issue has been automatically marked as stale because it has not been commented on for at least three months.
The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.
Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.
-
rails
- State changed from open to stale