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

Problem in : Building simple Ruby application - Adding a dropdown

Hi,

I seem to be stuck in this video. I followed along with all of the code, but somehow if I enter 1 as a value when making a new status, it doesn't seem to match up with any names. I made a few registratrions and also tried other values (2, 3, 4, etc....) to see if that would match up.

Is there any way to check user id 's per registration in a database?

Thanks for your help!

Olivier

3 Answers

Jason Seifer
STAFF
Jason Seifer
Treehouse Guest Teacher

Hey Oliver,

Can you zip up your project files and email them to help@teamtreehouse.com?

Naomi Freeman
STAFF
Naomi Freeman
Treehouse Guest Teacher

It seems that the whole thing goes a little off the rails in Rails 4. My names in the dropdown are invisible, Devise was a difficult redo (if you don't know what you're doing - it's attr_accessible to strong params AND a switch between model and controller, even though the controller doesn't yet exist) and somehow everything ended up trying to branch, even though I only have one project.

A friend in the same course I'm taking (we're taking a live course) is following along and doing all the things exactly as you say and his is beautiful. He's also on the wrong version of Rails.

Sad dinosaur.

Jason Seifer
STAFF
Jason Seifer
Treehouse Guest Teacher

Hey Naomi Freeman that's true. Rails 4 was just recently released and we're still planning content for it. In the mean time, try following along with Rails 3.2.14. Sorry about that!