I've recently installed editableviews and am experiencing a flood of update notification triggered from rules when I update a value in a view. Editable Views is updating all nodes in the view regardless whether the data has changed for the entity or not. Basically, I update one value in a view containing 25 rows I receive update notifications for all 25 rather than for the one that has a changed value.

I'm using the beta8 build.

Comments

sata’s picture

Category: Bug report » Feature request

Upon reviewing the code in the current dev release, I see that in editableviews.module line 222 - 224 there is a comment that entities could be updated needlessly as there is not comparison between old data and updated data. For me this is crucial to the production use of this module as the users would be quite irritated and confused in receiving content update notifications needlessly. I'll set aside some time to see how difficult a comparison would be to implement.

If you have specifically excluded this feature for performance reasons (or any other reason) please let me know so I can take your input into factor. I'll update the category from "bug report" to "feature request" to reflect.

joachim’s picture

Status: Active » Closed (duplicate)
Issue tags: -rules

> Editable Views is updating all nodes in the view regardless whether the data has changed for the entity or not.

There's already an issue for this.

Also, please don't randomly tag issues without understanding the issue tag guidelines.

> If you have specifically excluded this feature for performance reasons (or any other reason) please let me know so I can take your input into factor. I'll update the category from "bug report" to "feature request" to reflect.

See the comments in the code and the other issue! The problem is that it's not always possible to determine whether a node has changed or not.