设计3 Rails 4不允许的参数

Question

This is what I'm getting when signing up: Unpermitted parameters: password_confirmation WARNING: Can't mass-assign protected attributes for User: email, password I have installed everything and am trying devise out first time. I have created a model user and everything should be smooth. This is a fresh installation of devise first user sign up. No default code has been altered. Please help!

PROBLEM SOLVED: I added attr_accessible to my user.rb model

Answer 1

Check your User model and see if the parameters are accessible.

Keep in mind you don't need to name them, IE my User model looks like this with devise 3 and rails 4:

class User < ActiveRecord::Base
  # Include default devise modules. Others available are:
  # :confirmable, :lockable, :timeoutable and :omniauthable
  devise :database_authenticatable, :registerable,
         :recoverable, :rememberable, :trackable, :validatable, :confirmable

  validate :username, presence: true, uniqueness: true, format: { with: /[a-zA-Z0-9]{4,20}/ }
end

Solution Rahul is talking about doesn't make much sense as these parametters are already permitted on the requests, but in my case, I have an extra username attribute for this User model so I added to ApplicationController:

  before_filter :configure_permitted_parameters, if: :devise_controller?

  protected
  def configure_permitted_parameters
    devise_parameter_sanitizer.for(:account_update) << :username
    devise_parameter_sanitizer.for(:sign_up) << :username
  end

Answer 2

add following in your ApplicationController (if u have Rails4)

before_filter :update_sanitized_params, if: :devise_controller?

#  method to sanitized params for devise user sign up
def update_sanitized_params
    devise_parameter_sanitizer.for(:sign_up) {|u| u.permit(:email,:password, :password_confirmation)}
end

for more info see https://github.com/plataformatec/devise#getting-started "Strong Parameters" section

Answer 3

If anyone else is getting this error still, check your form url path. I had copied the session_path into the form that should have used registration_path.

Answer 4

I'm doing my first use of Devise GEM (currently learning rails) with this exercise. In my case, I had the same error and it was a routing problem.

The issue was on a form_for in the new.index.html.erb of the devise/registrations views folder .

The form had a url: session_path(resource_name) , but in order to work it should point to registration_path(resource_name) .

I changed that and now it is working on heroku.

This is a link to the file.

And this is the exercise live on heroku: devise.muga.com.co