Should unpublished content appear in the emails sent out to subscribers of specific content types? At the moment, this is what is happening to me with beta 9.

Comments

gustav’s picture

Version: 5.x-2.0-beta9 » 5.x-2.0-beta10

I think that notifications of unpublished nodes should not be sent out except to users who have the privilege to publish it. This can be implemented by modifying subscriptions_mail_cron() but before creating a patch I will wait a day to see what others think.

siliconmeadow’s picture

I may have made a mistake in posting this as an issue. I see in the publishing part of the workflow that there is a checkbox for sending subscription notifications and the help below says:

Subscriptions does not send notifications for unpublished nodes (except to users who have the administer nodes permission)

I need to see what's happening in other roles - ones with out administer nodes permission.

salvis’s picture

Category: bug » support
Status: Active » Fixed

This should already work as intended. I've just added the following text to README.txt:

Unpublished Nodes/Comments
--------------------------

Subscriptions does not send notifications for unpublished nodes/comments 
except to users who have the 'administer nodes' / 'administer comments'
permissions. The
   !is_unpublished
   !comment_is_unpublished
variables let you mark unpublished nodes/comments, as demonstrated
in the default templates.

Publishing a node/comment will cause a notification to be sent to all 
subscribers. This does not currently work for bulk-publishing nodes
via admin/content/node, though.

Please reactivate the issue if it needs further clarification or if it doesn't work as described.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

salvis’s picture

Version: 5.x-2.0-beta10 » 5.x-2.0-beta12
Status: Closed (fixed) » Fixed

I have now also implemented notifications on bulk publishing.

(The README.txt update didn't make it into BETA12.)

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.