NoMethodError报错排查：为何会出现该错误？

Hey Jasmine, let's break down why you're hitting that NoMethodError with your controller code. There are a few key issues to check, starting with the most obvious one:

1. Missing set_genre Method #

You’ve added before_action :set_genre for the show, edit, update, and destroy actions—but you never defined this method in your controller! When Rails tries to run those actions, it looks for set_genre and can’t find it, which directly triggers a NoMethodError.

This is an easy fix: add the private set_genre method (plus the missing genre_params method your create action relies on) to your controller:

class GenresController < ApplicationController
  before_action :set_genre, only: [:show, :edit, :update, :destroy]
  before_action :authenticate_user!, except: [:index, :show]

  def index
    @genres = Genre.all.order("created_at desc")
  end

  def show
  end

  def new
    @genre = current_user.genres.build
  end

  def edit
  end

  def create
    @genre = current_user.genres.build(genre_params)
    respond_to do |format|
      if @genre.save
        format.html { redirect_to @genre, notice: 'Genre was successfully created.' }
      else
        format.html { render :new } # Don't forget to handle save failures!
      end
    end
  end

  # Add these private methods
  private

  def set_genre
    @genre = Genre.find(params[:id])
  end

  def genre_params
    # Permit the actual fields your Genre model uses (adjust as needed)
    params.require(:genre).permit(:name, :description)
  end
end

2. Unestablished Model Associations #

If the error reads undefined method 'genres' for #<User:0x0000...> or nil:NilClass, you probably haven’t set up the association between your User and Genre models correctly:

• In your User model, add has_many :genres
• In your Genre model, add belongs_to :user (and ensure your genres database table has a user_id integer column—run a migration if it doesn’t)

Without these associations, current_user.genres won’t exist as a valid method, leading to the error.

3. Issues with current_user #

Even though you have authenticate_user! protecting new and create, if your Devise setup is misconfigured (or current_user isn’t returning a valid User object for some reason), current_user could be nil. Calling .genres on nil will throw undefined method 'genres' for nil:NilClass.

To debug this, temporarily add a check in your new method:

def new
  raise current_user.inspect # This will show you what current_user returns when you load the page
  @genre = current_user.genres.build
end

If this outputs nil, double-check your Devise installation and make sure you’re logged in when accessing the new genre page.

Start with fixing the missing set_genre method first—that’s the most likely culprit here. Let me know if you still run into issues after checking these points!

内容的提问来源于stack exchange，提问作者Jasmine Anderson