The subscriptions module puts new (unpublished) nodes in a queue and doesn't send notifications out until the node is published. This is especially useful when you're moderating your content and a) Don't want notifications going out before content is approved/published and b) Do want notifications to go out to users who've subscribed to "Notify me of new posts".

The current approach of the Notifications module treats new content that's moderated as updated content. This makes it impossible for users to get notifications for new/moderated content unless they subscribe to to be notified of updates instead of new posts.

Thank you,
Kevin

Comments

richardeholder’s picture

richardeholder commented

This capability is integral to our needs to switch from Subscriptions to Notifications.

ohzone’s picture

ohzone commented

As a site moderator this feature is important - I don't want notifications going out until content is actually published and viewable by subscribers and/or the general public

kmillecam’s picture

kmillecam commented

I have some sponsorship money if someone is interested in working on this feature.

Kevin

hsjones’s picture

hsjones commented

This functionality is key for my large commercial customers who must moderate content, so I strongly support the feature request.

Scott Jones

Veggieryan’s picture

Veggieryan commented

If anyone else wants to step up to the plate, I am gearing up to tackle this.

I have an employer that needs this for a project and it is obviously super important but I don't want to do parallel efforts.

contact me via my profile if you are coding or funding.

lets get a great patch ready to be committed.

hope to hear from someone soon so I know what needs to be done and what is preferred by the notifications maintainers.

jose reyero’s picture

jose reyero commented
Status: Active » Closed (duplicate)

See #285226: Redefine notifications and node/comment approval workflow