Debug quickly why the plugin isn't working
Make sure the Notification plugin and all the extensions are up-to-date!

Notification v7 uses WordPress' REST API to render the recipients field. You must ensure the /notification endpoint is accessible and the API is accessible.

To debug the missing message (Carrier execution) please enable the Notification log in Notification > Settings > Debugging. All the executions will be caught there.
Please make sure the notification suppressing checkbox is turned off if you wish to send the message to the public.
If the notification gets caught, you can inspect the details (ie. if the recipient is set correctly) and if they seem to be ok, check if your WordPress is sending the emails (SMTP is set correctly?) or it can connect to the API (depends on the selected Carrier).
If the notification is not there, you probably found a bug. Please report it on Github.

Most of the time this is caused by the post editor saving the content multiple times. Ie. Gutenberg saves the main content in one request, taxonomy terms in another request, ACF saves the fields in another request, and so on.
Please activate the Background Processing feature to prevent this from happening.

This might be related to the content encoding. You can try to define email header (activate that in Notification -> Settings -> Carriers -> Email) as follows:
text/html; charset=UTF-8


This error will most likely occur in tandem with: Warning: ftp_nlist() expects parameter 1 to be resource, null given
To make sure the plugin works, please add the following to your wp-config.php:
if (!defined('FS_METHOD')) define('FS_METHOD', 'direct');
Copy link
On this page
The Recipients field is empty
Nothing is sent
Multiple Notifications are sent
Weird characters are being sent in the email
Cannot see the Custom Post Type on the Triggers list while creating a Notification
Storage templates base path: .../wp-content/plugins/notification/src/templates must exists and be a directory