Subscriptions Don't Send on Node Publish, only on Node Creation

wouldn't simplenews and the simplenews digest modules be a better fit for this task?

You are right, it's supposed to send out on publish, not on (EDIT: unpublished) creation, with one exception: users with the administer nodes permission (who can see unpublished nodes) will get notification of unpublished nodes.

So, be sure to do your testing with a non-administrative account!

Shouldn't the Subscription module send email subscriptions on content when that content is set to "published" and not just on node creation?

You are right, it's supposed to send out on publish, not on (EDIT: unpublished) creation...

If this is true then I disagree entirely with this model.

Drupal's access layer is such that any number of different 3rd party modules are applied resulting in a set of nodes shown to the visitor. It sounds like the Subscription module would send notification of new content to users who may NOT be able to view the content due to:

• Organic groups
• Workflow
• Rules
• etc...

I looked through Subscription's documentation and found nothing about what triggers the subscription notification or whether it observes this common access model. Does anyone know if it follows the access rules?

@mudd: Of course, Subscriptions follows the node access model. I happen to also be the maintainer of the ACL and Forum Access modules.

The OP (gregarios) didn't follow up, so I assume my explanation has cleared up the issue.

@salvis: Sorry, I should have installed it and tested before I posted.

Here's some quick testing results (I'm glad to post this, because I need exactly this well thought-out module -- Thanks salvis!)

I'm using Workflow, have Subscriptions set to send notice As soon as possible, and test by executing cron through the Devel module.

While subscribing to both content-type being tested AND taxonomy terms AND I'm subscribing to the terms I'm testing with:

• Indeed, the notification email seems to happen as the new node becomes accessible AND cron runs, not at creation time,
• Only first taxonomy term match is shown in notice email, (it would nice to list all terms/vocabularies matched rather the only first match)
• If the node is created with 1 set of terms, then edited to different terms, upon making accessible via Workflow and running cron the email tells me I matched the 1st set of terms,
• If the node is created without any terms, then edited to add terms, then made accessible, the email doesn't include that I matched any terms,

While ONLY subscribing to a set taxonomy terms:

• If the node is created with taxonomy terms, then edited and the terms removed, then made accessible, the email is sent with the terms chosen at creation time,

While subscribing to content-type at the time node is created BUT unsubscribing before it's made accessible:

• I don't get any notification email.

--- EDIT: I just want to be clear on my meaning here ---

My application is in a very non-casual setting, so I'm hoping to help by being nitpicky (I hope you don't mind).

Since my users may take weeks to format a node (mine are very large projects, with sub-nodes attached, etc etc) it would make sense for the Subscriptions matching to not take place at publish time (for me, but not necessarily all Workflow users). (and since workflow requires a node to be published all the while it passes through its states). But, I totally understand there wouldn't be much logic having Subscription make its check via the node access hooks because that would happen only when, and every time, a user views the node.

So I'm thinking of making patch for workflow users that provides a check box to disable the matching at publish time, and make an action available for workflow. Of course, there are lots of issues to iron out, and I'm a newbie (yikes!) so I'll try my best.

Does this make sense? If yes then I'll start a new thread and stop cluttering this one. Thanks!
---End edit---

It seems that Subscription records taxonomy matches at node creation time, but content-type matches at some different point. Since I'm using workflow, and I allow users to come back and edit their nodes before they submit for review, I'd like the Subscription check to be made at the time the node become accessible.

Would it be possible to change the responsible function to an Action (or have a configurable option) so I could fire it off by a workflow state-change trigger? This might make it very flexible. If the maintainer is open to this idea then I could take a stab at it.

Thank you for your detailed checking and accounting.

Your requirements are very specific — we'll have to work on this...

I see you've created #520230: Proposed Action plugin (e.g. for workflow) in the meantime — let's continue over there, because this goes way beyond the subject of this thread.