Odd one this. I created a custom subscription for a Newsletter Content type, with a view to subscribing 1700 existing members, as well as all new ones. In User Management I ticked the first page of users and they all subscribed perfectly. Move to page 2. No joy, always says "0 users have been subscribed".

CommentFileSizeAuthor
#8 notifications_custom-1099530-8-D6..patch1.12 KBroball
#3 1099530.patch634 bytesliquidcms
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bboybenny’s picture

bboybenny CreditAttribution: bboybenny commented

I am having exactly the same problem too, only the first page of users (50 users) have been subscribed.
For other pages, always returns 0 users have been subscribed.

liquidcms’s picture

liquidcms CreditAttribution: liquidcms commented

actually if you add 1 or more to a specific custom subscription; then you can no longer add any others to that same subscription.

yes, i see this as well... working on fixing it now.

4.x branch certainly not ready from prime time as i have found 5 bugs in past 3 days trying to set this up - but i think maintainer is on hiatus from this project... and i need Anonymous support.. so trying to sift through the issues and fix what i can.

liquidcms’s picture

liquidcms CreditAttribution: liquidcms commented
FileSize
1099530.patch634 bytes

and fixed... on to the next

liquidcms’s picture

liquidcms CreditAttribution: liquidcms commented
Status: Active » Needs review
amanire’s picture

amanire CreditAttribution: amanire commented

Patch worked for me, thanks!

nicktr’s picture

nicktr CreditAttribution: nicktr commented

Worked for me too!

roball’s picture

roball CreditAttribution: roball commented
Title: User Subscription failure » "0 users have been subscribed." on users Update option "Add subscription for selected users"
Priority: Normal » Major
roball’s picture

roball CreditAttribution: roball commented
Status: Needs review » Reviewed & tested by the community
FileSize
notifications_custom-1099530-8-D6..patch1.12 KB

Have successfully tested liquidcms's patch and it definitely fixes this bug - thank you!

I have rerolled the patch against the latest 6.x-4.x code using the format Drupal currently expects (patch -p1). Please, can it be committed?

miro_dietiker’s picture

miro_dietiker
Location Switzerland
CreditAttribution: miro_dietiker commented
Status: Reviewed & tested by the community » Fixed
Issue tags: +Needs tests

Fixed this also.
Tests would be great also...

roball’s picture

roball CreditAttribution: roball commented

Thanks for committing this critical fix. Good to know somebody again cares about this useful module.

Status: Fixed » Closed (fixed)

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

dimitriseng’s picture

dimitriseng CreditAttribution: dimitriseng commented

Hi, I have not checked this on 7.x but it looks major. Can you please confirm whether this issue would also exist in 7.x and if yes, could this patch be ported? Thank you.