Currently, when a node is modified twice within the notification interval, we can create the following message:

Updates for [node type]: [title]
- The [node type] has been updated.
- The [node type] has been updated.
Read more [node-url]

We would like to access more of the detailed node revision and/or event information when nodes are updated. The dblog module's report has detailed information for the event, including the acting user and a timestamp; however, I don't see how to capture this information in the notifications / messaging module.

Updates for [node type]: [title]
- The [node type] has been updated by "user A" at 12:00...
- The [node type] has been updated by "user B" at 12:05...
Read more [node-url]

What are we missing? Many thanks.

Comments

stacysimpson’s picture

stacysimpson commented

Anybody have any advice for how to capture the node revision and/or event information in the content notifications? I've been trolling around the 'notifications_content.module' file, but don't see any obvious places.

jose reyero’s picture

jose reyero commented

You can add the user info by using the right tokens, not sure about the revision, you may need to create a new node token for it..

stacysimpson’s picture

stacysimpson commented

Jose, thanks for the suggestions. We've tried the built-in user tokens; however, from our testing, none of them map the user who actually made the change which initiated the event. "Currently logged in user" seems to be a global variable which can't be used for sites with multiple contributors and users navigating and editing topics concurrently. Node author is exactly that...the node author, not the user who made the change. Are we missing a set of tokens in our install or missing something else?

Any other suggestions are appreciated.

jose reyero’s picture

jose reyero commented
Status: Active » Closed (duplicate)

> Any other suggestions are appreciated.

Yes, please don't post issues more than once #384562: Like access to more detailed event information

(the tokens, the user who inititated the event is the logged in user, who else?)