0

I am a beginner and I have used this fix (https://medium.com/@nejdetkadir/how-to-use-devise-gem-with-ruby-on-rails-7-33b89f9a9c13) for making devise work with turbo forms in my previous project and it worked fine. But when I use it in my new project it gives me an

undefined local variable or method rendering_options' for #<TurboDeviseController::Responder:0x00007f9684019cb8 @controller=#<Devise::RegistrationsController:0x0000000000bbd0>, @request=#<ActionDispatch::Request POST "http://localhost:3000/users" for ::1>, @format=:turbo_stream, @resource=#<User id: nil, email: "", created_at: nil, updated_at: nil>, @resources=[#<User id: nil, email: "", created_at: nil, updated_at: nil>], @options={}, @action=:new, @default_response=nil>

error when I sign-up without filling any fields(or passing invalid info in any of the form fields). My previous project seems to be working just fine and I have recreated this error three separate times just to be sure.

For reference here are my:

devise controller file: https://pastebin.pl/view/d275fa93

devise rb file: https://pastebin.pl/view/1b80a0bb

console output : https://pastebin.pl/view/abee4b18

screenshots of error: https://paste.pics/49220ee8d4a60bd874f539e689b32c07, https://paste.pics/286c88869865db2e996ce039a3d5eac3

Rohan James
  • 13
  • 2
  • Welcome to Stackoverflow! [Please don't post screenshots of text/data/code/errors.](https://meta.stackoverflow.com/questions/285551/why-should-i-not-upload-images-of-code-data-errors/285557#285557) They can't be searched or copied, or even consumed by users of adaptive technologies like screen readers. Instead, paste the code as text directly into your question/answer. If you select it and click the {} button or Ctrl+K the code block will be indented by four spaces, which will cause it to be rendered as code. Please edit your question to turn the image into well-formatted text. – Koedlt Feb 08 '23 at 15:35

1 Answers1

2

I was also struggling with this exact problem when I stumbled upon this article written in Japanese: https://qiita.com/gazayas/items/0726f9ffa093e4e2d772

Changing

render rendering_options.merge(formats: :html, status: :unprocessable_entity)

to

render error_rendering_options.merge(formats: :html, status: :unprocessable_entity)

fixed the problem for me. Apparently it is caused by responders updating to 3.1.0.

Cory Walker
  • 36
  • 3