Problem/Motivation
Sort of a bug report/ sort of a feature request. Module homepage says it can do these two things:
- generate email notifications when content was added, updated, or deleted; and
- generate email notices about content that had gone 6 months without being reviewed
If you eg, don't use (1) every insert/update/delete of a node triggers a logger message like "Simple content notifications is installed but not configured.". Yet it can be configured eg for option (2) only.
Steps to reproduce
Configure only review notifications
Save any node
Watch logs get filled
Proposed resolution
Add an option to disable the logger
Remaining tasks
MR/Patch on the way
User interface changes
Adds a settings option to the admin config form, provides an update hook to maintain status quo (ie, enabled logging)
API changes
None
Data model changes
None
Comments
Comment #3
scott_euser commentedComment #4
scott_euser commentedComment #5
scott_euser commentedAlso combined patch attached for #3372256 + #3372260 since these have a merge conflict in the update hook (since both require a new update hoo)
Comment #6
aaronpinero commented@scott_euser I am thinking that I might, while working on the other issue, split this into two configuration options so logging for each type of notification (content updates vs content review) can be enabled/disabled separately. Right now, the option makes it seem like this option is just for logging with content update notifications.
Comment #7
scott_euser commentedMakes sense to me given there are two config pages, will update the MR with this shortly.
Comment #8
scott_euser commentedUpdated the MR splitting into two configurations. Thanks!
Comment #10
scott_euser commentedThanks! Changed to fixed since its committed.