Ruby on Rails Treebook — Customizing Forms:Creating Relationships Error

A different approach/

I explored a bit of the Action Controller:Exception page that came up when I hit the "NoMethodError in Statuses#show" It was there that I noticed a way to get the id for the user. By clicking the "show session dump" link towards the bottom I found the following:

warden.user.user.key: ["User", [4], "$2a$10$6ncjHnBWUS8uHVO65e1/xe"]

When following the video I assumed that my user_id was 1, in-fact it was 4. By using that value (4) where I had previously used 1, the errors went away.

I'll still be checking out sqlitebrowser though ;-)

-Thanks!

I have to say this worked for me: Inside application_controller.rb:

  # Prevent CSRF attacks by raising an exception.
  # For APIs, you may want to use :null_session instead.
  protect_from_forgery with: :exception
  before_action :configure_permitted_parameters, if: :devise_controller?
  protected
  def configure_permitted_parameters
    devise_parameter_sanitizer.for(:sign_up) { |u| u.permit(:first_name, :last_name, :profile_name, :email, :password, :password_confirmation) }
  end
end

then I dropped, recreated and migrated my db

rake db:drop

rake db:create

rake db:migrate

deleted all statuses in console

rails console

Statuses delete_all

exit

ran the server

rails server

signed in at /user/sign_up

then only after creating a few statuses did both views work for me. Status>Show and Status>Index.

So remove those lines from show, and index. At that point delete all your post you had before them. Once you delete all your pots before that re-add those lines and see if it works.

Oh Teh, after a few hours of frustration I think I just got through my error. I'll post this for reference to anyone else with the same issue as it seems it's common for this tutorial.

According to a response from the instructor Jim, on another user's entry:
"NoMethodError in the case of models is usually a symptom of the database not having the right columns. Since you didn't have the method :user_id, and it was a column we were adding at that point in time, I would guess that you may have forgot to migrate the database, or the migration may have failed the first time around."

I also ran rake db:migrate again and it did not solve the error. I have already gone through the Michael Hartl RoR tutorial and we had used SQLite Database Browser. sqlitebrowser.sourceforge.net/ (I'm using 2.0 but some have to use 1.1 if you run into trouble.) In taking a look at the database information I wanted to see if all of my columns were there. [I apologize but apparently you can't paste images into this forum.]

After opening Treebook's development.sqlite3 file with the browser software I saw the right columns but in clicking into the ["Browse Data" tab : Table drop down :statuses] I could see that the user_id cell was 0. I figured this was the fraking nil that was causing the error so I manually changed it in SQLite Database Browser to 4 to match the id cell count.

Then I saved and went right to check the site and I could get back to all the pages that were crashing before making the change. There's probably a way to fix this through the Rails Console but if you're receiving nil errors this could be why. Also SQLite Database Browser is a handy tool for visual checks of what's sitting in the dev database.

Hope this helps.

Namaste

Tulio --- this method saved me! I rather wish Treebook would link forum comments to the videos so I could quickly find how people have screwed up during a step and gotten themselves out of it.

Tulio --

I'm sort of lost. I found the warden key and for me it says 2. How do I change that to 1?

HELP!