I have a number of different node types. There's a specific node type for which I do not want users to receive updates. I have disabled their ability to subscribe to the node type, but when I publish or update the node they receive an email anyway. The only way to prevent this is to uncheck the "send subscriptions notifications" checkbox when I create or edit those nodes. As you might imagine, this gets really old.

Furthermore, I have another node type where I also do not want users to receive notifications. I have a user role that allows certain users to create/edit this node type. I have the same user role's ability to "administer nodes" disabled, which means they can't even get to this checkbox. So when they submit a new node of this particular node type, it will automatically send out the notification.

It'd be nice if there were a way to do one of the following:
1) Have a setting in "admin/settings/subscriptions" for each node type as to whether or not this box is checked or unchecked by default.
2) Have a setting in "admin/settings/subscriptions" for each node type as to whether or not this box even appears based on node type.
3) Both 1 and 2.
4) Or possibly best yet.... Have settings for both 1 and 2 in "admin/user/access" based on node type vs user role.

Does this make sense?

Immediately, I simply need to turn off the notification check box for a specific node type.... but I can see there being even more functionality with further development.

Any ideas for the immediate issue?

Comments

salvis’s picture

salvis
he/his
commented
Status: Active » Postponed (maintainer needs more info)

Your users receive a notification for a node type to which they can't subscribe (i.e. don't have the permission to subscribe)? Are you sure about this? Are you sure they're not receiving the notifications because of some other subscriptions, e.g. to a taxonomy term? or a subscription to a node?

You can set a content type to unlisted or blocked. That should cover your needs.

Send subscriptions notifications is in the Administration fieldset, which appears only for users that have the administer nodes permission. Being able to set the default state of the checkbox is a nice idea, but we're already suffering from UI overload...

RobertNelsonVance’s picture

RobertNelsonVance commented
Status: Postponed (maintainer needs more info) » Active

Hmmm....

Here's what seems to be happening:

1) On the "admin/settings/subscriptions" page node type "Foo" is set as "unlisted" in the "unlisted content types" select box.
2) On the "admin/settings/subscriptions" page node type "Foo" is set as "blocked" in the "blocked content types" select box.
3) When you go to create a new node "Foo", the "send subscriptions notifications" checkbox appears and is checked under the "publishing options" field set.
4) When the new "Foo" node is saved, it is included in the Subscriptions notification emails.

There are no other subscriptions settings setup for taxonomy, etc.

Is this unintended behavior?

salvis’s picture

salvis
he/his
commented

There is the subscribe to all content types permission (which user 1 has, of course), which overrides everything else.

#3 is working as designed — there's no mechanism to change the default state.

If you're testing as user 1, that would explain #4. Are you seeing "Foo" in red, with a mouse-hover hint?

salvis’s picture

salvis
he/his
commented
Status: Active » Closed (won't fix)

Feel free to reopen, if you have something to add.

kgeographer’s picture

kgeographer commented

imho -- it would in fact be very useful if every time a minor edit is made to a subscribe-able node it didn't require the editor to scroll down and uncheck the "send subscriptions notifications" checkbox. it's easy to forget when you're tweaking the appearance of a page and the result is peppering subscribers with multiple announcements. nice module, by the way.

kg

salvis’s picture

salvis
he/his
commented

@satchinsb: Sorry, but you're adding to an issue that doesn't match your concern and that has been rejected.

There is at least one matching issue in the queue...