Databases
StackOverflow2013
Postsdbo
POForbiddenAttributesError, Devise
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POForbiddenAttributesError, Devise
    primarykey
    data
    text
    <p>I allow users to login using Facebook and Google using OmniAuth, also I allow them to create accounts using their emails. Everything is working fine except for the part in which the users are able to update their account information. </p> <p>I added a field called username, in which the sign_up and sign_in handles Ok, for the update I don't want to require the user enter password if he is signed in using facebook but I keep getting ForbiddenAttributesError.</p> <p>here is the code I wrote. </p> <pre><code>class Users::RegistrationsController &lt; Devise::RegistrationsController before_filter :configure_permitted_parameters, if: :devise_controller? def update @provider = Provider.find_by_user_id(current_user.id) @user = User.find(current_user.id) email_changed = current_user.email != params[resource_name][:email] is_omniauth_account = @provider.blank? successfully_updated = if is_omniauth_account resource.update_with_password(params[resource_name]) else resource.update_without_password(params[resource_name]) end if successfully_updated # Sign in the user bypassing validation in case his password changed sign_in @user, :bypass =&gt; true redirect_to root_path else clean_up_passwords(resource) render_with_scope :edit end end protected def configure_permitted_parameters devise_parameter_sanitizer.for(:sign_up) { |u| u.permit(:username, :email, :password, :password_confirmation) } devise_parameter_sanitizer.for(:account_update) { |u| u.permit(:username, :email, :password, :password_confirmation, :current_password) } devise_parameter_sanitizer.for(:sign_in) { |u| u.permit(:username, :email, :password) } end def resource_params params.require(:user).permit(:username, :email, :password, :password_confirmation, :current_password) end private :resource_params end </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChris Peters
    1. USMohammad Abu Musa
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POForbiddenAttributesError, Devise
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POForbiddenAttributesError, Devise
      1. USThanh
      1. VTFavorite
    3. VO
      singulars
      1. POForbiddenAttributesError, Devise
      1. USAlkindi
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload