The notify.php script allows a site administrator to configure Pm Wiki to send email messages whenever pages are changed on the wiki site. Notifications can be configured so that multiple page changes over a short period of time are combined into a single email message (to avoid flooding mailboxes).
This feature is useful for sites and pages that have infrequent updates, as it eliminates the need to frequently check RecentChanges pages just to see if anything has changed.
In order for notifications to work, the notify.php script must be enabled in the site's local customization. Usually this is as simple as placing the following in local/config.php:
This says that information about page changes should be periodically emailed to email@example.com. The Site Admin.Notify List? page can contain multiple "notify=" lines to cause notifications to be sent to multiple addresses; the "notify=" lines can be concealed by placing them inside of an
NOTE: Do not put any spaces around the equal sign! Notifications will fail silently if you have... This is a really easy mistake to make because all of the other assignments have spaces around the equal sign.
firstname.lastname@example.org rather than notify = email@example.com
The basic syntax is
A number of options exist for limiting the pages that result in a notification. The
# send notifications about the Main group to firstname.lastname@example.org
# notify email@example.com of any changes to the home page
firstname.lastname@example.org name=Main.Home Page
# notify email@example.com of changes to pages except in Main
(Note: The options are similar to the PageList syntax.)
For maintaining arbitrary lists of pages, i.e., "watchlists", it's generally easier to build a trail of pages to be watched. The following entry in Site Admin.Notify List? will send firstname.lastname@example.org an email containing changes to any of the pages listed in the Profiles.Alice trail:
# notify Alice of changes to pages listed in Profiles.Alice
Note that once this entry has been added to Site Admin.Notify List?, Alice can easily change her watchlist by editing the Profiles.Alice page, and doesn't need to edit the Site Admin.Notify List? page. In particular, this means that an administrator can restrict editing of Site Admin.Notify List?, yet allow individuals to maintain custom watchlists in other pages.
Limitations of this feature:
This is probably a good place to point out that edit access to Site Admin.Notify List? should be controlled, otherwise malicious persons can use the notification capability to flood others' electronic mailboxes. By default, Site Admin.Notify List? is blocked against reading or edits except by the admin (as is the case for most pages in the Site Admin group).
Adding notification entries via local customizations
Notification entries can also be added via the
Controlling notification frequency
To prevent flooding of recipients' mailboxes, the notify script uses a "squelch" value as the minimum amount of time that must elapse between messages sent to any given email address. The default squelch setting is 10800 seconds (three hours), which means that once a recipient address is sent a notification message, it will not receive another for at least three hours. Any edits that occur during the squelch interval are queued for the next notification message.
The site administrator can change the default squelch interval via the
# enable notifications
# Alice receives at most one email per day
# Bob can get notifications hourly
email@example.com trail=Profiles.Bob squelch=3600
# Charles uses the site default squelch
Controlling notification delay
Because a page will often receive several edits in rapid succession (e.g., a long post followed by several minor edits), a site administrator can also set a
# enable notifications
Note that the squelch and delay values are minimums; notifications are sent on the first execution of Pm Wiki after the delay period has expired. For inactive sites, this could be much longer than the specified delay periods. This isn't really considered an issue since timely notifications are less important on relatively inactive sites. However, changes within the squelch time after the last notification will remain unnoticed if the wiki is not even visited for a long period after. If this matters it might be necessary to make the server call pmwiki.php regularly (e.g. cron job).
firstname.lastname@example.org trail=Profiles.Edgar delay=600
Note for Windows installations
Sites running PHP under Windows may not have PHP's mail function configured correctly. Such sites may need to add a line like
to config.php, where smtp.server.com is the name of your host's preferred outgoing mail server. You may also need to set the sendmail_from value if that is not configured:
Notification only for major edits
It is possible to send notifications only in case of major edits. In your config.php, replace "
if ( @$_POST['diffclass'] != 'minor' )
This way, only 'major' edits send notify messages (when the author doesn't select the checkbox for minor edit). If you want minor edits and not major edits to send the message then you would use:
if ( @$_POST['diffclass'] == 'minor' )
Disabling notifications for downloads
If you use "$EnableDirectDownloads=0;" (eg. for privacy on a password-protected wiki) then attached images may generate duplicate notification messages. To prevent that disable notifications for downloads via
if ( $action != 'download' )
That way, only page views (and not images within the page) will generate notifications. See PITS:01159 for more information.