Devise配置需求：支持普通用户自主注册与管理员代注册

Hey there! Let's get your dual registration flow (self-signup + admin-assisted signup) working properly with Devise. I'll break this down step by step, starting with cleaning up your routes and adding the controller logic you need.

First, let's fix your routes.rb—the resources :devise line is redundant because devise_for :users already generates all the standard Devise routes for authentication, registration, etc. We'll add custom routes specifically for admin-initiated signups:

# config/routes.rb
devise_for :users, path: 'devise'

devise_scope :user do
  # Admin-specific registration routes
  get 'users/registrations/admin_new', to: 'users/registrations#admin_new', as: :admin_new_user_registration
  post 'users/registrations/admin_create', to: 'users/registrations#admin_create', as: :admin_create_user_registration
end

These routes point to a custom controller action we'll build next, so admins have a separate flow from regular users.

Devise's default RegistrationsController is designed for self-signup, so we'll create a subclass to add admin-specific logic. This lets us keep the default self-signup flow intact while adding our admin features.

# app/controllers/users/registrations_controller.rb
class Users::RegistrationsController < Devise::RegistrationsController
  # Make sure only logged-in users can access admin actions
  before_action :authenticate_user!
  # Restrict admin registration actions to admins only
  before_action :ensure_admin!, only: [:admin_new, :admin_create]

  # Render the admin registration form
  def admin_new
    build_resource({})
    respond_with self.resource
  end

  # Handle creating a user from the admin form
  def admin_create
    build_resource(sign_up_params)

    if resource.save
      set_flash_message! :notice, :signed_up
      redirect_to admin_users_path # Redirect to your admin user list or preferred page
    else
      clean_up_passwords resource
      set_minimum_password_length
      respond_with resource
    end
  end

  private

  # Check if the current user is an admin (adjust this to match your admin check logic)
  def ensure_admin!
    unless current_user.admin?
      flash[:alert] = "You don't have permission to do that."
      redirect_to root_path
    end
  end

  # Permit any extra attributes you need for user creation (e.g., role, name)
  def sign_up_params
    params.require(:user).permit(:email, :password, :password_confirmation, :name, :role)
  end
end

Note: Adjust the ensure_admin! method to match how you flag admins in your User model (e.g., if you have a role column, check for current_user.role == 'admin').

Create a view file for the admin registration form—you can base it on Devise's default signup form, but tweak it for admin use:

# app/views/users/registrations/admin_new.html.erb
<h2>Create New User (Admin)</h2>

<%= form_for(resource, as: resource_name, url: admin_create_user_registration_path) do |f| %>
  <%= render "devise/shared/error_messages", resource: resource %>

  <div class="field">
    <%= f.label :email %><br />
    <%= f.email_field :email, autofocus: true, autocomplete: "email" %>
  </div>

  <div class="field">
    <%= f.label :password %>
    <% if @minimum_password_length %>
      <em>(<%= @minimum_password_length %> characters minimum)</em>
    <% end %><br />
    <%= f.password_field :password, autocomplete: "new-password" %>
  </div>

  <div class="field">
    <%= f.label :password_confirmation %><br />
    <%= f.password_field :password_confirmation, autocomplete: "new-password" %>
  </div>

  <!-- Add any admin-only fields here, like user role -->
  <div class="field">
    <%= f.label :role %><br />
    <%= f.select :role, User.roles.keys.map { |role| [role.humanize, role] } %>
  </div>

  <div class="actions">
    <%= f.submit "Create User" %>
  </div>
<% end %>

This form submits to our custom admin_create action, and includes fields admins might need to set (like assigning a role).

The standard user self-signup flow remains intact thanks to devise_for :users—users can still access /devise/sign_up to register themselves without any extra changes.

Quick Notes on Your Original Code #

• The resources :devise line was redundant and could cause route conflicts, so we removed it.
• Your initial approach to using devise_scope was on the right track—we just expanded it to add dedicated admin actions instead of trying to repurpose Devise's default routes.

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