I have configured Subscriptions to be used on Taxonomy terms only, and users can subscribe to 'Categories' of content.

When I create new content for subscribed terms, I see the data appear in the subscriptions table for the appropriate tid when I create the node. The send interval is also set to 'As soon as possible'. However, I don't get any email that a new node was added to my chosen terms.

Am I missing some configuration setting?

Comments

salvis’s picture

salvis
he/his
commented

Did you enable the subscriptions_mail.module? Did you run cron?

kevinquillen’s picture

kevinquillen commented

Yes, I enabled the subscriptions_mail module.

Users can only subscribe to Taxonomy terms, to which nodes are categorized. When I create a new node and assign it to a term a user has, shouldn't it queue a mail to send?

salvis’s picture

salvis
he/his
commented

Yes. You already confirmed that it was queued.

Did you run cron? Well, in the meantime, cron should have run, I guess...

kevinquillen’s picture

kevinquillen commented

Yeah, I ran cron. I never saw a record in subscriptions_queue.

salvis’s picture

salvis
he/his
commented

When I create new content for subscribed terms, I see the data appear in the subscriptions table for the appropriate tid when I create the node.

I never saw a record in subscriptions_queue.

Hmm...

Users can only subscribe to Taxonomy terms, to which nodes are categorized. When I create a new node and assign it to a term a user has, shouldn't it queue a mail to send?

I would say so, yes, but maybe you try subscribing to updates of an existing node and edit it and see what happens, just to get into the feeling...

kevinquillen’s picture

kevinquillen commented

Well okay, let me back up then, to see if we are on the same page about how this module actually functions:

What I need is to have a content type with taxonomy attached to it (Categories), like a Blog, and when new content is posted and given a category, anyone who subscribed to that taxonomy term gets an email or daily digest of new content. I don't want any emails going out when a node is updated or when a term is added/updated, only when new content appears for a category.

Can this module do that? Has anyone been able to get it to do that? If so, perhaps I have configured it incorrectly but it wouldn't appear to be.

salvis’s picture

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

Yes, it can, and it's straight-forward, but you're describing strange things.

When I create new content for subscribed terms, I see the data appear in the subscriptions table for the appropriate tid when I create the node.

I never saw a record in subscriptions_queue.

These two statements seem to contradict each other, although I'm not sure whether you're mixing up the table names or what. Data appears in the {subscriptions} table when you create a subscription, not when you create a node. OTOH, data appears in the {subscriptions_queue} table when you create a node that matches a subscription.

Users can only subscribe to Taxonomy terms, to which nodes are categorized.

That is complete nonsense.

When I create a new node and assign it to a term a user has, shouldn't it queue a mail to send?

Usually, you assign a term to a node while creating the node (not the other way around). If a user is subscribed to that term, then he will get a notification. I don't know what you're describing.

Please realize that we're in beta test. It's possible that some features are is not yet working correctly. If you want to be part of a beta test, then you're expected to try to work things out on your own and find out where the problem is, if there is one. Other sites are apparently using Subscriptions successfully, so it's not that it doesn't work at all. Try a content type subscription, or a page subscription, new or update, etc., and if you have something that works, then work towards what you'd like to do, and find out where things start to go wrong.

kevinquillen’s picture

kevinquillen commented

Sorry, yes, I see records appear in the main subscriptions table when I create a node, but never in subscriptions_queue. In the main table I see users who have subscribed to Taxonomy terms by their tid.

I have an tech blog in development where posts are added daily under different categories. Users can see these categories and subscribe to them (Apple, MS, Open Source, etc). When an admin creates a blog post and adds the term 'Apple' to it, anyone who has subscribed to that term from their profile or blog section should be queued to receive an email about new content, but that never happens for me (test users are set to receive as soon as possible, I also tried 15 minutes, never saw a queue or email).

Users can only subscribe to Taxonomy terms, to which nodes are categorized.

This is basically what I mean.. someone subscribes to 'Apple' taxonomy term, they are not allowed to subscribe to nodes or users. When nodes are created and tagged with terms, users subscribed to those terms should receive something.

salvis’s picture

salvis
he/his
commented

I think we have to conclude that it will not work for you, and that we can't find a common language. Sorry...

Maybe someone else can help you...

kevinquillen’s picture

kevinquillen commented

I am confused because the comment in the subscriptions_taxonomy module says:

If a user subscribes to a term he will receive notifications each time a node is published to that taxonomy term.

However that's not happening for me. No mail goes out, no queue is created.

I'm not sure how simpler to explain it.

kevinquillen’s picture

kevinquillen commented

Okay, I saw that the Subscription Notification on the node type was disabled, and have set it to New Nodes.

This time, I got an email. However, it was blank, and the email headers did not have any content other than where it originated... still looking...

kevinquillen’s picture

kevinquillen commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

Solved..

  1. Setup Content Type to send Subscription Updates on New Nodes (I missed this step somehow)
  2. Subscribe to Terms
  3. Edit the Mail Template
  4. Create a node, add some taxonomy to it
  5. Run cron

Now I get emails and can edit template(s) as I see fit.

salvis’s picture

salvis
he/his
commented

Setup Content Type to send Subscription Updates on New Nodes (I missed this step somehow)

All the default send options are on by default. You must have turned them off at some point.

Thanks for pulling through and letting us know.