subscriptions + taxonomy access, need privilege to administer nodes to work?

I was having this same problem, I found that switching to cron based notifications actually fixed the issue. Hope this helps.

How did you ever figure this out? It has been driving me nuts!

I have a similar problem but it is even worse: for me, not only does the person posting have to have "adminster nodes privileges", but even then, notices are only sent to users who have "adminster nodes privileges", which is obviously not a realistic option. Any help on this will be much appreciated.

subscribing

subscribing

I have the same problem. It occurs in 4.7 and 5.1. I stepped through with the debugger, and found that the "administer nodes" privilege is one of the mechanisms that allows a notification to be sent. Hence, it gets sent when the administrator posts a forum topic.
A second mechanism to allow the notification occurs when the node access is tested. This one fails for any user, since the the node hasn't been created at this point, and the proper privileges haven't been added to the node_access table yet. Hence the "cron based" notification might work, since this might allow the node to be created first. This last part I have to verify. (Comment notification works by the way because here the node (top post) already exists.

Other than that it seems that there needs to be an additional check if the subscription user has access in general to a new node, or something like that. Or maybe first create the node (entry in node_access table), and then do the notification.

If someone has a proper solution please let me know.

I now verified that using cron for sending notifications in general works. Therefore, I chose this setting.
I then found, however, that the cron comment-notification does not do all the checks the non-cron comment-notification does. So I had to add a few lines in the cron portion of the notification processing.
I also corrected a few things that I favor personally:
-If a comment is posted, it sends a teaser of the comment (if the user had chosen this setting). Before it sent a teaser of the node (top post), or it sent the full comment (depending on subscription type).
-Since the comment wasn't available for certain subscription types, I added the the comment_id as an additional parameter

I attached a MS Word file that should show the changes I made using the "compare" function. Maybe someone can make use of it, or let me know if I introduced any further errors.

This all does not solve the "non-cron" setting. Here still someone would have to see
-what can be done that the node_access-table entry doesn't exist at the time of notification.
-why the user who changed the node is checked for "administer nodes". Maybe this is not necessary.

subscribing

I tried to give the subscriptions module a higher weight (using the moduleweight module) to try if it gets executed after the node_access is created. No luck, the non-cron based subscription mode still didn't send out notifications when a node was created (only when updated or when a comment was created/updated). So I am still back to using the cron based notification. Does anyone have a similar problem?

subscribe

I think I have the same problem on Drupal 5.1 with version 1.9...

Same problem, same reason (I presume).

5.x-2.0 is a complete rewrite, therefore any bugs in it are new. All prior releases will be obsolete when 5.x-2.0 final is out. Closing references to bugs in prior releases for this reason. Please help test 5.x-2.0 betas. Thank you!