I'm aware that you're currently working on a patch (yes, I looked at the queue!) to try to disable notifications by content type. Since that's not working, and I'm about to update my site with a lot of pictures (which would generate a lot of notifications), what should I do to prevent those notifications from going out? Or can I?
Basically, if I turn off notify, upload the content, and then turn notify back on, will the updates go out? Or do I have to wait for my notification time period to expire, and then turn it back on? Or will it detect there hasn't been a notification sent out about these updates, and it will send them out no matter how long I have notify turned off?
Comments
Comment #1
gisleI happy to report that notifications can be disabled by content type.
In addition, in the latest release of the 7.x branch, there has been added a control to the user interface (Truncate queue) that can be used for the effect you want. It truncate the notification queue, so that notifications that up to that point has been queued for being sent on the next cron run, will not be sent.
This issue is fixed for the 7.x -branch. It will not be backported to the 5.x-branch, since that is no longer supported.
For your mass update use case, you can either disable notification for the picture type, or you can use the following procedure:
And to answer your questions:
Yes, they will. Notify builds its queue from all nodes that has been published since the last time a batch was sent or the queue truncated. Toggling Notify on and off have no effect on the queue.
The latter. But now, you can prevent it from going out by truncating the queue.
Comment #2
gisleFixed typo in title.
Comment #4
gisleBug: Need to add a spurious comment to remove from queue.