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 Josh Flowers
Josh Flowers
7,010 Points

NoMethodError in Statuses#new

I keep getting this error when clicking "new status"

NoMethodError in Statuses#new undefined method `name' for #<Status:0x007f863ba56ba8>

<div class="field">
       <%= f.label :name %><br>
       <%= f.text_field :name %>
     </div>
     <div class="field">
       <%= f.label :content %><br>

Could this be that I'm using rails v4 and that attr_accessible is no longer in use?

I'm re-watching the video: Generating the Devise Views and I don't know where to put the :first_name , :last_name , :profile_name ...could this be the reason why I'm getting the error?

2 Answers

Warsama Gabriel
Warsama Gabriel
3,570 Points
Warsama Gabriel
Warsama Gabriel
3,570 Points

yeah I had the same problem! I was just getting ahead of myself when I was clicking around on my treebook app and couldnt post a new status I thought something was wrong and I was back tracing for a few hours thinking I messed up somewhere, then I realized that Jim didnt get to the part of the "new status" problem.

Josh Flowers
Josh Flowers
7,010 Points
Josh Flowers
Josh Flowers
7,010 Points

Nevermind. This was part of the lesson as Jim fixes this issue in the next video.

Suggestion: I think in Jason's last video, he should mention that this creates a problem. It seems that this hiccup has tricked many people, as we don't want to keep going through the videos if we think our code is wrong.

Otherwise, great videos!