I have a site with a content type that is both blocked and unlisted. The role with the 'subscribe to all content types' is an administrators role with two users. Despite this, a normal user received a digest message which included a notice that a node for this content type was added. This should not have happened. I'm going to dig through to find out why, but any pointers would be appreciated.

Comments

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Category: bug » support
Status: Active » Closed (works as designed)

Seems it was a simple issue, that the users had subscribed to the content type before it was added to the blocked & unlisted lists.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Title: User received digest with notice for blocked/unlisted node » Unsubscribe users when settings changed that would not allow them to subscribe
Category: support » feature
Status: Closed (works as designed) » Active

As a follow-up, maybe there should be a way to unsubscribe users from lists when the configuration is changed to where they would now be blocked from doing so?

salvis’s picture

salvis
he/his
commented

Thanks for pursuing this.

Notifications for nodes of blocked content types should be eliminated in cron (through _subscriptions_content_access()). Is there any doubt whether this is working?

We seem to have a problem with unlisted content types (and omitted vocabularies!) though. Maybe we should add a subhook where we pass the {subscriptions_queue} row and ask for confirmation that this notification should really be sent. This would give the submodules a chance to weed out unwanted notifications.

I'd prefer that over permanently destroying data (such as removing an unknown set of content type subscriptions).

salvis’s picture

salvis
he/his
commented
Issue summary: View changes
Status: Active » Closed (outdated)