class ApplicationController < ActionController::Base
  # Prevent CSRF attacks by raising an exception.
  # For APIs, you may want to use :null_session instead.
  protect_from_forgery with: :exception
end

class ApplicationController < ActionController::Base
  # Prevent CSRF attacks by raising an exception.
  # For APIs, you may want to use :null_session instead.
  protect_from_forgery with: :exception

  before_filter :configure_permitted_parameters, if: :devise_controller?

  protected

  def configure_permitted_parameters
    devise_parameter_sanitizer.for(:sign_up) << :name
  end
end

Add 'name' to strong parameters for Devise
Add 'name' to strong parameters for Devise

Since strong parameters are handled in the controllers in Rails 4,
devise needs to be told to allow the 'name' field in the user
registration form to be passed to the model for record creation. If
this isn't done, the field may be filled in by the user but the
parameter won't make it to the model and record creation will fail with
an empty name.
