Rails中基于Wicked Wizard与Devise的分步注册布尔值跟踪需求问询

Got it, let's break down exactly how to build this flow where users confirm their email first, then complete a 3-step profile setup, with a boolean flag to track when their profile becomes visible.

1. Setup Required Gems #

First, add these gems to your Gemfile and run bundle install:

gem 'devise'       # For authentication and email confirmation
gem 'wicked'       # For multi-step wizards

2. Configure Devise: Add Confirmation & Progress Tracking #

a. Generate Devise User Model (if not already done) #

Run this command to set up the User model with confirmable enabled:

rails generate devise User
rails db:migrate

b. Add the profile_completed Boolean Field #

We need a flag to track if the user finished Step 1 (required for profile visibility). Generate a migration:

rails generate migration AddProfileCompletedToUsers profile_completed:boolean default:false
rails db:migrate

c. Update User Model & Devise Config #

In app/models/user.rb, make sure :confirmable is included in the Devise modules:

class User < ApplicationRecord
  devise :database_authenticatable, :registerable,
         :recoverable, :rememberable, :validatable,
         :confirmable # Enables email confirmation
end

Double-check config/initializers/devise.rb to ensure confirmable is enabled (it should be by default after generating the model with confirmable):

config.confirmable = true

3. Build the Wizard Controller for Profile Steps #

a. Generate the Wizard Controller #

Run this to create a wizard controller with your 3 steps:

rails generate wicked:wizard UserProfiles step1 step2 step3

b. Customize the Wizard Controller #

Update app/controllers/user_profiles_controller.rb to tie the wizard to the current user, and set profile_completed to true when Step 1 is submitted:

class UserProfilesController < ApplicationController
  include Wicked::Wizard
  steps :step1, :step2, :step3

  # Ensure only logged-in users can access the wizard
  before_action :authenticate_user!
  before_action :set_user

  def show
    render_wizard
  end

  def update
    @user.update(user_params)
    
    # Mark profile as visible once Step 1 is completed
    if step == :step1
      @user.update(profile_completed: true)
    end

    render_wizard @user
  end

  private

  def set_user
    @user = current_user
  end

  # Permit fields based on your step requirements
  def user_params
    params.require(:user).permit(:full_name, :bio, :avatar, :location, :other_step_fields)
  end
end

4. Configure Routes #

a. Customize Devise's Confirmation Redirect #

We want users to land directly on Step 1 right after confirming their email. Create a custom confirmations controller at app/controllers/users/confirmations_controller.rb:

class Users::ConfirmationsController < Devise::ConfirmationsController
  protected

  def after_confirmation_path_for(resource_name, resource)
    # Send confirmed users to the first step of the wizard
    user_profiles_path(step: :step1)
  end
end

b. Update Routes File #

In config/routes.rb, link Devise to your custom confirmation controller and add the wizard routes:

Rails.application.routes.draw do
  # Devise with custom confirmation redirect
  devise_for :users, controllers: { confirmations: 'users/confirmations' }

  # Wizard routes
  resources :user_profiles, only: [:show, :update] do
    get :step1, on: :collection
    get :step2, on: :collection
    get :step3, on: :collection
  end

  # Add your root route and other routes here
end

5. Create Wizard Step Views #

Create view files for each step in app/views/user_profiles/:

Step 1 View (step1.html.erb) #

<h1>Complete Your Basic Profile</h1>
<%= form_with(model: @user, url: wizard_path, method: :put) do |form| %>
  <div class="field">
    <%= form.label :full_name %>
    <%= form.text_field :full_name, required: true %>
  </div>

  <div class="field">
    <%= form.label :bio %>
    <%= form.text_area :bio %>
  </div>

  <%= form.submit "Continue to Step 2" %>
<% end %>

Repeat this pattern for step2.html.erb and step3.html.erb, adjusting fields as needed for each step.

6. Control Profile Visibility #

Wherever you display user profiles (e.g., a user's dashboard or public profile page), check the profile_completed flag to decide what to show:

<% if current_user.profile_completed %>
  <!-- Show full profile content -->
  <div class="profile-card">
    <h2><%= current_user.full_name %></h2>
    <p><%= current_user.bio %></p>
    <!-- Other profile details -->
  </div>
<% else %>
  <!-- Prompt user to complete Step 1 -->
  <div class="alert alert-info">
    Please finish your basic profile to access your full profile:
    <%= link_to "Complete Profile", user_profiles_path(step: :step1), class: "btn btn-primary" %>
  </div>
<% end %>

7. Extra Optimizations #

• Block direct access to later steps: Add a before_action to the wizard controller to prevent users from skipping Step 1:

  before_action :enforce_step_order, only: [:show]
  
  def enforce_step_order
    if (step == :step2 || step == :step3) && !@user.profile_completed
      redirect_to wizard_path(:step1), alert: "Please complete Step 1 first to proceed."
    end
  end
  

• Redirect on login: If a user logs in without completing Step 1, send them straight to the wizard. Add this to app/controllers/application_controller.rb:

  def after_sign_in_path_for(resource)
    if resource.is_a?(User) && !resource.profile_completed
      user_profiles_path(step: :step1)
    else
      super
    end
  end
  

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