Provide system action to write a db watchdog message [#2170013]

Rules provides several actions on behalf of core modules. For system we have drupal_message, redirect, mail etc but one common action missing from this list is drupal_watchdog. It is very useful to have the ability for a user rule to write to the db log. It just requires an extra entry in the rules_system_action_info() array in /modules/system.rules.inc and the corresponding function added to /modules/system.eval.inc

Patch coming up.

Comment	File	Size	Author
#2	2170013_2.rules_watchdog_action.patch	2.52 KB	jonathan1055
#2
#1	2170013_1.rules_watchdog_action.patch	1.54 KB	jonathan1055
#1

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

jonathan1055 CreditAttribution: jonathan1055 commented 9 January 2014 at 08:18

Status:

Active

» Needs review

File	Size
2170013_1.rules_watchdog_action.patch	1.54 KB

Patch against 7.x-2.6
The message category is currently fixed at 'Rules - custom' but this could be changed to a user text entry parameter.

Comment #2

jonathan1055 CreditAttribution: jonathan1055 commented 10 May 2014 at 13:34

File	Size
2170013_2.rules_watchdog_action.patch	2.52 KB

1 file was hidden/shown/deleted

File	Size
2170013_1.rules_watchdog_action.patch	1.54 KB

Here is an enhanced version, with the ability to specify the message identifier (column 1 in the dblog) and also to provide a link for the final column. Patch against 7.x-2.7

Comment #3

hargobind

he/him

Austin, Texas

CreditAttribution: hargobind commented 24 April 2016 at 21:13

Status:

Needs review

» Closed (duplicate)

There is an older thread at #1349882: Action: Create a watchdog entry where this feature is being discussed. Please merge your changes into that thread.
P.S. I like the configurability of the message identifier and link text in your patch.

Comment #4

TR CreditAttribution: TR commented 29 January 2019 at 04:37

I posted patch #2 to #1349882: Action: Create a watchdog entry in comment #34, as it is better than the patch that was being considered there. Please participate in that discussion to get this fixed!