This project is archived and is in readonly mode.
undefined method `protect_against_forgery?' for #<ActionView::Base:0x10ad1a500>
-
David Chelimsky
- Tag set to action_view, patch, testing
- Assigned user set to José Valim
-
David Chelimsky
- Assigned user changed from José Valim to Carl Lerche
-
David Chelimsky
- Assigned user changed from Carl Lerche to Yehuda Katz (wycats)
-
José Valim
David, I could not apply it. Could you please rebase?
-
David Chelimsky
I forgot there were two commits on that branch. In the previous commit I rearranged the tests in test_case_test. Here are the two commits (in order):
http://github.com/dchelimsky/rails/commit/44fda04e9a5e2d19a412104b5...
http://github.com/dchelimsky/rails/commit/53ba21a30fd359744cdee9acd...
If you want, I can squash them into one commit. If not, they should apply cleanly in that order.
Obrigado,
David -
Repository
- State changed from new to resolved
(from [e02db06ece7aeecec7c37f5b0e3de7d65c8684e6]) In AV::TC, move protect_against_forgery? from the test_case to the _helper module included in the view.
- ensures that protect_against_forgery? is present when a helper included in a partial that is rendered by the template under test calls it (which happens in FormTagHelper#extra_tags_for_form, for example).
[#4700 undefined method `protect_against_forgery?' for #<ActionView::Base:0x10ad1a500> state:resolved]
Signed-off-by: José Valim jose.valim@gmail.com
http://github.com/rails/rails/commit/e02db06ece7aeecec7c37f5b0e3de7...