公认的解决方案已经足够好了，但我看到两个问题:1) 所有的控制器都会检查当前控制器是否是设计控制器 (if: :devise_controller?) 和 2) 我们需要在方法中写入所有可接受的参数 (...for(:sign_up) {|u| u.permit(:bio, :name)})，甚至是 :email、:password 等等.

The accepted solution is good enough, but I see two problems: 1) All the controllers will check if the current controller is the devise controller (if: :devise_controller?) and 2) We need to write all the acceptable parameters in the method (...for(:sign_up) {|u| u.permit(:bio, :name)}), even the :email, :password and so on.

我认为更优雅的解决方案可能是:

I think that a more elegant solution could be:

# app/controllers/users/registrations_controller.rb
class Users::RegistrationsController < Devise::RegistrationsController
  before_filter :configure_permitted_parameters

  protected

  def configure_permitted_parameters
    devise_parameter_sanitizer.for(:sign_up).push(:name, :phone, :organization)
  end
end

# config/routes.rb
devise_for :users, :controllers => { :registrations => "users/registrations" }

注意:Rails 4.2+ 的更新

这个答案已经过时了:

• 将 Rails 4.2.1 和 Devise 3.4.1 的用户/注册"路径中的用户"更改为用户".
• devise_parameter_sanitizer.permit() 替换了 Devise 4 的 devise_parameter_sanitizer.for()(参见 Rails 5, Undefined method `for' for #<Devise on line devise_parameter_sanitizer.for)立>

• Change "users" to "user" in the "users/registration" path for Rails 4.2.1 and Devise 3.4.1.
• devise_parameter_sanitizer.permit() replaces devise_parameter_sanitizer.for() for Devise 4 (see Rails 5, Undefined method `for' for #<Devise on line devise_parameter_sanitizer.for)