Currently, I'm using usernodes. When I try to configure subscriptions, I can't get subscriptions to block sending notifications on usernodes updates. I have selected "unlist" and "block" in the content type of subscriptions configuration. Can anyone assist me? Thanks!

Comments

salvis’s picture

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

Are you testing with an account that has subscribe to all content types or with user 1?

Try a normal account.

limwork’s picture

limwork commented

I have not enable "subscribe to all content types". The notification is not sent to user 1 but the login user. As usernode is updated every time a user log in, a notification is send to the login user even for those without access control to subscriptions.

salvis’s picture

salvis
he/his
commented

If notifications are sent for user X, then there must exist a subscription for user X. How was that subscription created?

Use user 1 to look at the subscriptions of user X and remove the Usernode subscription.

limwork’s picture

limwork commented

I can remove the usernode subscription manually through each node but it is a tedious task to do it for all existing users and new users. I was wondering if I have done anything wrong in the configuration that prevent block content type to work. Thanks for the help!

salvis’s picture

salvis
he/his
commented

I wonder whether this is related to Auto-subscribe...

Who is subscribed?

Are you (as admin) creating users or are the users creating themselves?

limwork’s picture

limwork commented

The usernode is automatically created when my user sign up an account. I want users to auto-subscribe to content they have created but not usernode as they will get a notification every time they login or logout.

salvis’s picture

salvis
he/his
commented
Assigned: Unassigned » salvis
Category: support » bug
Status: Postponed (maintainer needs more info) » Active

Yes, I see, auto-subscribe overrides blocked content types. That's a nasty bug.

salvis’s picture

salvis
he/his
commented
Assigned: salvis » Unassigned
Status: Active » Fixed

Fixed in 5.x-2.x-dev. Give it up to 12h to be repackaged.

limwork’s picture

limwork commented

Thanks for the kind help and fast response!

salvis’s picture

salvis
he/his
commented

It turns out that my fix was broken.

Now fixed with #290882: Fatal error: Call to undefined function subscriptions_content_autosubscribe().

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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

limwork’s picture

limwork commented
Version: 5.x-2.2 » 5.x-2.3
Status: Closed (fixed) » Active

This issue resurfaced in version 2.3. Many thanks to have it fixes.

salvis’s picture

salvis
he/his
commented

The fix is supposed to avoid creating new auto-subscriptions for blocked content types. It does not remove old ones, because that should not happen anymore. IOW, you need to remove old Usernode subscriptions manually (see #4 above).

Are you saying that you have Usernode on the blocked list and you still get auto-subscriptions for newly created users?

salvis’s picture

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

@limwork: Please verify whether new users still create auto-subscriptions for their new usernodes.

salvis’s picture

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