In #505938: VBO, feature to execute bulk operations without updating node date you write, that node_save is called after executing an action.
I really need to avoid changing the node changed date, as I use the action to mark nodes as read. Currently this causes ping pong for user A and user B. If A marks nodes as read, they show up as updated for B and vice versa.
Is there a kind of action which doesn't call node_save, or where is this call? Could not find it in views_bulk_operations.module

thanks in advance

Comments

maulwuff created an issue. See original summary.

maulwuff’s picture

maulwuff CreditAttribution: maulwuff commented

I came accross
http://drupal.stackexchange.com/questions/30910/how-to-create-custom-vbo...
and the action_example module.
Even the action_example_basic_action which is labeled with 'Action Example: A basic example action that does nothing'
changes the node_changed timestamp.

is this a bug?

I also found out, that node_changed changes after the action has been executed. This means I can't keep the old "changed" value by UPDATE-ing it in my action.

maulwuff’s picture

maulwuff CreditAttribution: maulwuff commented
Title: Skip node changed update on action » Node is changed on every action
Category: Support request » Bug report
maulwuff’s picture

maulwuff CreditAttribution: maulwuff commented

#2545334: User wrongfully saved after Send e-mail action brought me to it: it is a bug. With the workaround mentioned there, the action_example_basic_action works as desribed in the docs.

Because of 

// Assume edit by default.
if (empty($this->operationInfo['behavior'])) {
  $this->operationInfo['behavior'] = array('changes_property');
}

every action without a dummy 'behavior' is treated like a changes_property-action.

GatorBat’s picture

GatorBat CreditAttribution: GatorBat commented

I'd just to add I'm having the exact same issue. I've used VBO for many years to mark nodes read using the following references:
http://drupal.org/node/1762#comment-5201854
http://drupal.org/node/515418

It's worked great until the 3.3 Security update. As @maulwuff stated, anytime a site user marks a node read, it pops up as new for anyone else.

Any idea how this can be fixed? I don't want to run an old version of the insecure module 3.2 just to have this as it previously did.

@maulwuff - does the behavior alteration/workaround mentioned in #3 of #2545334: User wrongfully saved after Send e-mail action work properly for you now?

joelpittet’s picture

joelpittet
Primary language English
Location Vancouver
CreditAttribution: joelpittet at The University of British Columbia commented
Status: Active » Closed (duplicate)

This is also a duplicate of #2254871: Default action behaviors in getAccessMask() which is where the problem I believe was introduced. Please try out and weigh in on the solutions.