I can't figure out what I am doing wrong:

created new rule: invoke on content update.
condition: content has type foo
condition: textual compare: line 1: [node:status] line 2: no (also tried numeric compare)
action: show configurable message on site

I have also tried to negate the textual compare as well....

So this should basically say: if content of type foo gets unpublished, then send a site message. No message shows up when the content gets unpublished. am I doing this wrong? could someone at least tell me if the node:status token is even working? been beating my head in for days just trying to get this to work. I have tried both the standard and dev versions of both WRG and token and nothing seems to work.

Comments

solidad’s picture

solidad commented

Sigh, I know why my actions wouldn't trigger....A user actually has to do the un-publishing of the node and NOT the system (like say from the admin area). Meaning that any nodes that get bulk un-published in the admin area won't fire the triggers. Is there a way to make a condition that doesn't rely on a user updating the node?

roper.’s picture

roper. commented

I'd like to know this as well...

I only installed this module because Userpoints doesn't allow you to give points when a node is published (it gives them as soon as it's submitted). So I used this in order to apply the action upon node-publish, but now I've run into this problem which really makes it no better than using moderated userpoints. (no offense meant, this module seems like it'll come in handy for other things at least).

Any help would be much appreciated. Thank you.

solidad’s picture

solidad commented

I am going to try to solve this issue, but It may take awhile because I am not much of a php person. What I am thinking is making "system" tokens. So you could use workflow-ng and just have a textual comparison and simply say: text 1: [node-mass-status] and text 2: yes. I am pretty sure that this can be done, but I have to find where the functions are for it. I'll try and keep you (and anyone else interested) posted.

fago’s picture

fago
Primary language German
Location Vienna
commented
Status: Active » Closed (works as designed)

>A user actually has to do the un-publishing of the node and NOT the system (like say from the admin area). Meaning that any nodes that get bulk un-published in the admin area won't fire the triggers. Is there a way to make a condition that doesn't rely on a user updating the node?

No, that's not possible. If a module properly uses node_save() to save it's changes everything is fine, however if some code writes directly to the database there is no possibility for us to detect that.

solidad’s picture

solidad commented

Hmm well that's frustrating....It completely negates the usability that I am looking for because I was hoping that I could get workflow-ng to fire on automated tasks such as mass delete or other system based actions. It just frustrates me that drupal has two kinds of deletes, publishing and all of the other node actions.

Thank you very much for the reply though.