Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trial
Wilson Usman
35,206 Pointsunpermitted paramaters and WARNING:
This is what it looks like in the console:
Unpermitted parameters: first_name, last_name, profile_name
WARNING: Can't mass-assign protected attributes for User: email, password, password_confirmation
This is happening after I try to sign up into the app. I'm actually on the Getting the Latest Changes tutorial.
I get this after I click sign up Sign up
2 errors prohibited this user from being saved:
- Email can't be blank
- Password can't be blank
Looks like since I'm on Rail 4 I get a lot of errors.
6 Answers
Brandon Barrette
20,485 Pointswell you're going to have to match your files to the project files. under each video, there is a link to the project files. Download them and compare. You should have to just change the models and controllers to match what is done in the project files.
Brandon Barrette
20,485 PointsYou should not use Rails 4 if you are trying to learn with these videos. In your gem file, add the version number next to rails, i.e.
gem 'rails', '3.2.12'
Once you have a handle on rails, you can then upgrade to rails 4 which moves these parameters from the model elsewhere.
Wilson Usman
35,206 PointsThanks Brandon, how will this affect the rest of the code I've changed because of the passed issues that have come to me because of not having 3.2 installed?
Brandon Barrette
20,485 PointsI don't know how far along you are, but I recommend learning in rails 3.2, then when you feel competent in rails, you can upgrade.
The main reason is that a lot of the gems that you may want to use in the future are not yet rails 4 compatible, and then you'll be stuck or have to spend countless hours finding a work around.
I'm still using rails 3.2 and won't be upgrading anytime soon until I'm fully ready and know that the gems I'm using are able to support it.
Wilson Usman
35,206 PointsI'm having a hard time just downgrading to 3.2, do you have a resource that might help?
Wilson Usman
35,206 PointsOkay thank Brandon, I really appreciate all your support!