When using editablefields with views, there is a 'Save' button but it is redundant because the fields update with ajax onBlur(). Please allow us to disable ajax and just use the 'Save' button.

Also, this is very confusing from a usability point of view, why is there a save button and ajax? A user would surely assume there was an option to use one or the other, but there isn't.

Original report:

its quite annoying sometimes we need to select all the editable fields then click save to do a bulk save and for that we need to disable the ajax functionalities when we do a select change in the editable fields, can we have an option of disabling the ajax?

help appreciated.

thank you

Comments

albert9000’s picture

Disabling Ajax would be greatly appreciated feature. +1

I'm guessing this could just be commented out in the code. Has anyone tried that?

boby_ui’s picture

I tried it seems to break some part of the code

leex’s picture

Issue summary: View changes
gillarf’s picture

Yes I would like to disable ajax as well. In my case, I would like to use and editable field in a panel page. Some of the panes on the page use the value of the field to determine whether to be shown or not. I can write some JS to do the same thing, but I think this will be a good feature.

gillarf’s picture

*removed my own incorrect posting*

g33kg1rl’s picture

Is there any plans to pursue this? Or provide a way to select one or the other?

joelpittet’s picture

Category: Support request » Feature request
Priority: Major » Normal

Feel free to propose a patch

hondaman900’s picture

+1 on this.

Right now I'm hacking my Views to force a page refresh in order to see the results of an editable field change calculate throughout the view (since the editable field ajax save doesn't update the view). I put the following simple code in a Global Text Area my view/view attachment footer. The user clicks the "Accept Changes" button which reloads the page with results of that edit showing throughout the View.

<button onclick="myFunction()">Accept Changes</button>

<script>
function myFunction() {
    location.reload();
}
</script>

However, the "Please wait..." ajax spinning wheel increases the row height when that editable field loses focus, which pushes my table down, which moves my "Accept Changes" button from under the users mouse cursor (!). Moving the script to the header instead avoids that but is less intuitive for the user.

The bigger issue with the automatic ajax update is that if my user goes straight from editing the field to click my "Accept Changes" button (the intuitive thing to do), it's a crap shoot as to whether the edit has time to reach the database and is captured before the page reloads. I really need to wait for the ajax update to the database to finish before clicking the "Accept Changes", otherwise I run the risk of calling a page refresh before the field is updated in the database.

For me (and I suspect many others) the best solution would be for the ajax callback to change the database and then finish the job by updating the view so that the results are seen, as well as the results of anything else in the view dependent on that value.

So, I'm sharing my hack if it helps anyone else, and asking if there's a way for the edit to not only hit the database but update the view.

Thanks.

OFF’s picture

+1 We need this feature to.

similar discussion is here:
https://www.drupal.org/project/editablefields/issues/1172174