I have a site that only employs the use of taxonomy terms for subscriptions.
for example I can create a "Case"(content type) node with a taxonomy term of IBM, and publish that to the site. Site users can then subscribe to the taxonomy term IBM and whenever that case is updated or a new case with IBM is created then the user should receive a subscription notification.
The site sends subscription notifications as expected for "NEW" 'Case'(s) about IBM to the subscribers, but when I update an existing 'Case' nothing is sent to the subscriptions_queue table. I have verified the configuration and the content type settings to make sure that they will trigger on node update and I double-check the 'send subscription notifications' box in the publishing options of the node before I save.
Any help is appreciated.
-Trevor
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | subscribe_to_red.png | 6.37 KB | salvis |
Comments
Comment #1
break9 commentedthis bug exists in versions 6.x-1.2 and 6.x-1.1 also
Comment #2
salvisThis is not what I'm seeing here. Here's what I did on my test installation:
1. Created my favorite vocabulary 'Colors' and enabled it for the content type 'story'.
2. Created a 'story' node and gave it the term 'red'.
3. Used phpMyAdmin to empty the {subscriptions} and {subscriptions_queue} tables.
4. Subscribed to 'red' and verified that 'On update' was checked on the user/1/subscriptions/taxa page (see screenshot).
5. Edited the 'story' (changing the title) and saved it.
6. Found two node/tid/TID entries in the {subscriptions_queue} table with the NID of my story as the load_args.
I don't remember why I get two entries (and don't care to investigate), but getting multiple entries in the queue is normal and subscriptions_mail deals with that.
AFAICS that's all I can do for you. Ultimately, you'll have to install a test site with a virgin Drupal + Subscriptions and repeat my test. Then find out what's different on your production site...
Comment #3
break9 commentedThis made me think. I have "on updates" set as a user default preference but I must have had this disabled in previous versions of the module. So I jumped in the the DB 'subscriptions' table to verify the on_update user settings and sure enough only the most recently subscribed content was being set up to receive notifications on updates. I ran a quick sql command to update the 'send_updates' field for all subscriptions in the table and I am good to go.
Sorry to waste your time thanks for the help.
-Trevor
Comment #4
salvisGood, thanks for letting us know.