I think I've found a mistake in Rails tutorial

At the point of this section
http://ruby.railstutorial.org/chapters/sign-up#sec-signup_failurehttp://ruby.railstutorial.org/chapters/sign-up#sec-signup_failure
clicking the “Create my account” button on the signup form shows the
following image at

http://ruby.railstutorial.org/images/figures/signup_failure_rails_4.png
According to the tutorial, I must modify these files to rid myself of
the
error.

  • app/controllers/users_controller.rb
  • app/views/users/new.html.erb
  • app/views/shared/_error_messages.html.erb
  • app/assets/stylesheets/custom.css.scss

I made all the modifications (until I saw the working
image
http://ruby.railstutorial.org/images/figures/signup_error_messages_bootstrap.pngto
the 4 files), and I still get the error image above when submitting the
file, rather than a page that shows me that I left the fields blank.

Can you help with this?

On 21 October 2013 18:35, desbest [email protected] wrote:

app/assets/stylesheets/custom.css.scss

I made all the modifications (until I saw the working image to the 4 files), and
I still get the error image above when submitting the file, rather than a page
that shows me that I left the fields blank.

Can you help with this?

Please don’t use images, copy/paste the error and short segments of
code here. First make sure you have checked the values of any
variables (params for example) by checking the values passed in
log/development.log and using puts to print values into the server
window.

Are you using exactly the versions of ruby, rails and gems expected by
the tutorial?

Colin

There is no params as I am just clicking a Signup button that’s on a
page,
then the error shows up.
I’m using Ruby 1.9.3 and the latest versions of sass-rails and
coffee-rails.

There is no params as I am just clicking a Signup button that’s on a
page,
then the error shows up.
I’m using Ruby 1.9.3 and the latest versions of sass-rails and
coffee-rails.

development.log says this

Started POST “/users” for 127.0.0.1 at 2013-10-21 19:35:27 +0100
Processing by UsersController#create as HTML
Parameters: {“utf8”=>“✓”,
“authenticity_token”=>“OhWhPfhLH/3EDeb19LG9u96gu+FUY3cPa+ZdsPN01q8=”,
“user”=>{“name”=>"", “email”=>"", “password”=>"[FILTERED]",
“password_confirmation”=>"[FILTERED]"}, “commit”=>“Create my account”}
Completed 500 Internal Server Error in 1ms

ActiveModel::ForbiddenAttributesError
(ActiveModel::ForbiddenAttributesError):
app/controllers/users_controller.rb:12:in `create’

On Mon, Oct 21, 2013 at 1:40 PM, Jordon B. [email protected]
wrote:

One should not claim a tutorial is broken before finishing it, because
clearly further down:
http://ruby.railstutorial.org/chapters/sign-up#sec-strong_parameters

To add since I neglected to mention it like I should have, just
because your form is blank does not mean there are no params, blank or
not it will create a param as the form still sends the fields, that is
why you see them listed there with “”. “” is not a null value, it is
an empty value, empty != null, nil == null because even a blank value
is a value to all systems. This is why Rails has .blank? and
.present? so you can work around this situation, but tbh you should
not need to as after you permit them and then pass them into the model
it should have already done a validator stating that you do not wish
it to be blank or null.

Thanks for your help. It turns out I missed something out. (Figure 7:22)

On Mon, Oct 21, 2013 at 1:37 PM, desbest [email protected]
wrote:

Parameters: {“utf8”=>“✓”,
“authenticity_token”=>“OhWhPfhLH/3EDeb19LG9u96gu+FUY3cPa+ZdsPN01q8=”,
“user”=>{“name”=>"", “email”=>"", “password”=>"[FILTERED]",
“password_confirmation”=>"[FILTERED]"}, “commit”=>“Create my account”}
Completed 500 Internal Server Error in 1ms

ActiveModel::ForbiddenAttributesError
(ActiveModel::ForbiddenAttributesError):
app/controllers/users_controller.rb:12:in `create’

One should not claim a tutorial is broken before finishing it, because
clearly further down:
http://ruby.railstutorial.org/chapters/sign-up#sec-strong_parameters

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs