捐赠Web应用表单仅首次关联current_user问题求助

Hey there, let's work through this problem you're hitting with your donation web app. It's frustrating when the first donation links correctly to current_user, but subsequent donations for the same donee save to the database without that user association. Let's break down the likely causes and fixes based on the code snippet you shared.

First, Let's Validate the Core Create Logic #

From your snippet, you're starting off right with current_user.categories.new in the new and create actions—but let's make sure this pattern holds every time you create a new donation category. Here's what to check:

1. Ensure You're Always Building the Category Through current_user #

Double-check your full create action to confirm you're never using Category.new directly (which would skip the user association). Your code should look like this:

def create
  # Critical: Always build the category via current_user to auto-set user_id
  @category = current_user.categories.new(category_params)
  
  if @category.save
    redirect_to some_path, notice: "Donation recorded successfully!"
  else
    render :new
  end
end

If you ever switch to Category.new, the user_id won't be populated automatically—even if you pass it in params (which you shouldn't do anyway, for security).

2. Verify Your Strong Parameters #

Make sure your category_params method isn't accidentally filtering out necessary associations, and also that you're not trying to pass user_id through the form (you don't need to, since current_user.categories.new handles this):

private
def category_params
  # Only permit fields that should come from the form—user_id is set via the association
  params.require(:category).permit(:amount, :category_type, :donee_id)
end

3. Check Nested Route Logic (If Applicable) #

If you're creating categories through a nested route like /donees/:donee_id/categories, you need to make sure you're associating both the user and the donee correctly without breaking the user link:

def create
  @donee = Donee.find(params[:donee_id])
  # Tie the category to both current_user and the selected donee
  @category = current_user.categories.new(category_params.merge(donee: @donee))
  
  if @category.save
    redirect_to @donee, notice: "Donation added to this donee!"
  else
    render :new
  end
end

This ensures the user_id is still set via current_user, even while linking to the donee.

4. Debug the Current User Session #

It's possible that for subsequent requests, current_user is unexpectedly nil (e.g., session timed out, or the form is submitting without maintaining the session). Add a quick debug log to confirm:

def create
  Rails.logger.debug "Current User ID: #{current_user&.id}" # Check logs for this value
  @category = current_user.categories.new(category_params)
  # ... rest of your code
end

If the log shows nil for subsequent requests, you'll need to fix session persistence (e.g., ensure your form uses form_with with proper authenticity tokens, or check your authentication middleware).

5. Confirm Model Associations #

Make sure your models are set up correctly to enforce the user-category relationship:

# app/models/category.rb
class Category < ApplicationRecord
  belongs_to :user, optional: false # Enforces that every category has a user
  belongs_to :donee
end

# app/models/user.rb
class User < ApplicationRecord
  has_many :categories, dependent: :destroy
end

The optional: false constraint will throw an error if a category tries to save without a user, which helps catch issues early.

Quick Recap #

The root issue almost always boils down to not building the category through current_user for subsequent requests. Stick to current_user.categories.new every time you create a donation, verify your session stays active, and ensure your model associations enforce the link.

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