Notify is a simple, lightweight notification module. It provides e-mail notifications to subscribers about updates and changes to the Drupal web site.
Submit bug reports and comments via the project's issues queue on drupal.org.
If you enable node revisions node revisions, the notification e-mail will also mention the name of the last person to edit the node.
This module requires a supported version of Drupal and cron to be running.
The administrative interface is at: Administer » Configuration » People » Notification settings.
There are four tabs:
The Settings tab allow you to configure how the module shall work.
You can specify how often notifications are sent, the hour to send them (if the frequency is one day or greater), the number of failed sends after which notifications are disabled, and the maximum number of notifications to send out per cron run.
When setting how often notifications are sent, note that e-mail updates can only happen as frequently as the cron is set to run.
To reset the count of failed sends to zero, look at the notification settings in the user's profile and save it press “Save settings” (there is no need to change anything).
If you check “Include updated posts in notifications”, any change to a node or content will cause it to be included in the next notification. Note that even minor changes, such as correcting a trivial typo or setting or unsetting the “sticky” attribute for the node will flag it as updated, so use this option with caution in order to avoid excess notificatons.
If you check “Administrators shall be notified about unpublished content”, users belonging to roles with the “administer nodes” and “administer comments” permissions granted will receive notifications about unpublished content. This is mainly to make the module useful to manage moderation queues. Note that notifications about unpublished content are only sent once.
The “Watchdog log level” setting lets you specify how much to log. The setting “All” will make a log record of every notification mail sent. The setting “Failures+Summary” will only log failed notification attempts. It will also insert a summary of how many sent and how many failures at the end of each batch. The “Failures” setting will omit the summary. The “Nothing” setting will turn of logging for Notify.
The Queue tab is to process and inspect the notification queue.
The radio buttons below the heading “Process notification queue” has the following meanings:
The Status panel gives the administrator a rough overview of the current state of the notification queue.
If you tick the box “Bulk subscribe all users”, all non-blocked users that do not already subscribe to notifications will be subscribed with the initial settings set under the deafult tab.
The checkbox under “Notification default for new users” is used as the default value for the notification master switch on the new user registration. Note that this setting has no effect unless you grant the anonymous user the right to access notify.
The “Initial settings panel” let you set up the initial settings that will apply to new users registering, and to users that are enrolled in notifications with batch subscription. These settings have no effect on users that already have the master switch set to “Enabled”.
The final section under the Settings tab let you set up notification subscriptions by node type. Having nothing checked defaults to making all content types available for subscription.
The Users tab is to review and alter per-user settings for those users that have the master switch for notifications set to Enabled.
If you tick the box “Bulk subscribe all users”, all non-blocked users that do not already subscribe to notifications will be subscribed with the initial settings set under the deafult tab.