Rails 4 - best_in_place: Unprocessable Entity

Question

I'm using best_in_place to edit a field in a profile database managed with 'devise'. Everything updates fine in the edit view, but shortly after editing a single field with best_in_place the field returns to its original value, and the database has not been updated. NOTE: Running bundle install, restarting the server, and refreshing the page have not worked. users_controller.rb: ``` class UsersController < ApplicationController respond_to :html, :json ... def update @user = User.find_by_id(params[:id]) respond_to do |format| if @user.update_attributes(user_params) format.html { redirect_to(@user, :notice => 'Profiiile was successfully updated.') } format.json { head :ok } else format.html { render :action => "show" } format.json { render :json => @user.errors.full_messages, :status => :unprocessable_entity } end end end ... private def user_params params.require(:user).permit( :id, :first, :last, :email, :password, :password_confirmation, :remember_me, :user_phone, :user_birthday, :us…

Accepted Answer

Try replacing:

```
    format.json { head :ok }
```

with:

```
    format.json { respond_with_bip(@user) }
```

in your respond_to block in your controller.

respond_with_bip is a "utility method you should use in your controller in order to provide the response that is expected by the javascript side, using the :json format" https://github.com/bernat/best_in_place

EDIT:

Hmm, it might be that devise is expecting a password to update the user, and this is causing the rollback, since it can't find one. You can do one of two things: remove `:validatable` from devise in your User model, or add these two validation overrides to your User model, `validates :password, presence: true, length: {minimum: 5, maximum: 120}, on: :create` `validates :password, length: {minimum: 5, maximum: 120}, on: :update, allow_blank: true`

Rails 4 - best_in_place: Unprocessable Entity

Solution

Problem