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

Ruby

Posted by Adam Kelm
Adam Kelm
29,082 Points

Strong Parameters

Whenever I've added any attr_accessible values, Rails has been throwing me errors telling me to use the strong parameters instead of attr_accessible, so I've just had to ignore all those. Along with all the differences in the newer Bootstrap versions, it's been a frustrating course.

Here's an article I found explaining all the strong parameter errors, and how to go about fixing them: http://www.sitepoint.com/rails-4-quick-look-strong-parameters/. For anyone using Rails 4, or even 3.2.7 and above, it should help things. I think Treehouse would be wise to update this course a little, or even just add some notes explaining the discrepancies.

1 Answer

Jared Rader
Jared Rader
Courses Plus Student 4,445 Points

I agree the course should be updated, but you can specify that you want to use Rails 3.2 rather than Rails 4. The lesson is still very relevant, as many apps out there are still Rails 3 apps.

Using Rails 3, you don't have to worry about strong parameters, you can just use :attr_accessible

I'd suggest using Ruby Version Manager (rvm) to install various versions of Rails and Ruby and keep gemsets organized: https://rvm.io/