I have an easy question about several of the "events."

What do the following mean:

Content is going to be viewed

and

Content is going to be saved

What exactly are those events. It would seem, literally, that "content is going to be viewed" is any published content on the site--after all, it all is "going to be viewed." So what does that event mean? What triggers it? Same for "going to be saved."

Thanks,

Dan

Comments

nevets’s picture

Component: Rules Core » Rules Engine

Without looking at the code

"going to be viewed." will trigger when a node (content) is viewed as a whole (either teaser or full view).

"going to be saved" is trigger after a user clicks "submit" when add/changing content.

royerd’s picture

Hmm. OK. There's also an event: After saving new content

I suppose the operative word there is "new"? So "going to be saved" applies to all content (new or revised) an after saving new content applies only to new?

What is the difference between "after saving new content" and "content is going to be saved"?

I guess what throws me here is "going to be saved" and "going to be viewed"----"going to be"?? Am I thinking too hard about this?

dan

nevets’s picture

"Going to be ..." implies the trigger fires before the action, so "going to be saved" fires before the content has been saved.
In contrast "after saving new content" fires after the content has been saved.
And yes, you may be over thinking things :)

mitchell’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

CarbonPig’s picture

Would/should preview trigger "going to be saved" ?

gollyg’s picture

I believe the trigger 'going to be saved' is fired on the hook_nodeapi options of 'presave'. Details of this event can be found at http://api.drupal.org/api/drupal/developer--hooks--core.php/function/hoo....

Other events referenced in this thread refer to similar nodeapi options - e.g. 'node is going to be viewed' maps to the option 'view'.