Comment from: fplanque

This is the panel where you can control how outbound pings and notifications are sent out when a new post or a new comment gets published on your b2evolution installation.
Notifications include:
There are three options to determine the timing of when notifications should be sent:
When notifications are sent, a flag is set in the post and even if you unpublish the post and publish it again, the notifications will not be sent again. This is to avoid unwanted "spam".
When you set the "issue date" of a post in the future, it typically won’t be visible immediately (unless you change the default ).
Therefore, the notifications should not be sent out immediately either. They should be sent out at the time the post becomes public.
To resolve this, by using Asynchronous notifications, b2evolution can schedule notifications to go out in the future, at the desired date and time:
The sample posts installed by b2evolution are flagged as "notifications have already been sent". Thus, these posts will never try to send out notifications.
Additionally, when you run a test installation on localhost
, ping plugins will detect that sending out pings to public services would not allow anyone to see your posts and those pings will be skipped.
If you have a problem with the 30 second delay in a follow up comment see
https://forums.b2evolution.net/you-can-only-post-a-new-comment-every#c112017
Please leave a Feature Request/comment here if you ave a use case for: