Started with a fresh install of 4.7.1 with current 4.7 subscriptions as the only installed contrib module using all default settings. Subscription e-mails are sent correctly for thread and content type level subscription, but no subscription e-mails are sent for cateogry level subscriptions. The watchdog logs show nothing and nothing is coming into my test email accounts. I tested this using PHP 4.4.1 using both Apache 2.0.55 and IIS 5.1, and the behaviour is consistent across both webservers. Seems to be an issue when taxonomy subscriptions are involved. Can anyone else replicate this behaviour?

Comments

dziemecki’s picture

dziemecki commented

Is it possible that you are testing to see if you are being notified of your own posts?

brashquido’s picture

brashquido commented

Sorry Dan,

Been ridiculously busy the last week or so, I'll try and get in and retest this issue this week...

markusH’s picture

markusH commented

Hi,

we have a similar problem: if the taxonomy has free tagging switched on, there's no mails going out. subscriptions seems to ignore free tagging taxonomies.

Is there a way to fix this/work around this issue?

dziemecki’s picture

dziemecki commented

Can you explain this a little more? I'm not familiar with free tagging.

Are you saying that Subscriptions doesn't work at all if free tagging is enabled, or are you unable to subscribe to a free-tagged taxonomy?

markusH’s picture

markusH commented

We use two independent taxonomies to classify our content. One (call it "FixedList") is a fixed hierarchical structure which the user can't change (in the settings of the taxonomy free tagging is deactivated). The other one (call it "FreeList") is a plain list of keywords which can be extended by the users (free tagging activated).

Subscriptions to terms from the "FixedList" work as expected. But subscriptions won't work if you try to subscribe to terms from the "FreeList" - no mails send. Switching off the "Free Tagging" for the "FreeList" taxonomy solves the problem - but we do need the taxonomy to be extended by our users...

Hope this helps.

dziemecki’s picture

dziemecki commented
Title: Taxonomy subscription e-mails not sent » Subscription incompatible with free-tagging
Assigned: Unassigned » dziemecki

Changing the description

dziemecki’s picture

dziemecki commented
Category: bug » feature

I'm a bit torn on this one, guys. I think it's a dangerous precedent to start adding code that is only applicable to a single contributed module. I can tell you what the problem probably is, if one of you want to try and address it. I don't think this is a bug - just an incompatibility.

Around line #256, I start looping through term_data looking for taxa that a person might subscribe to. Your free tag taxa are probably not in there. One would have to copy down the normal taxonomy code and modify it for the free tagged stuff, where ever it's held. Then, you'd have to do the same thing just about everywhere else you see "term_data". And you'd have to add a new, separate 'free' subscription tag to keep any similar ID codes separate.

Not terribly simple, the way I see it.

dziemecki’s picture

dziemecki commented
Assigned: dziemecki » Unassigned

Turning project over to new owner.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented

I'm struggling with the same problem in pathauto and another solution (untested) is to move the subscriptions module later in the call of hooks (e.g. give it a heavier weight) so that taxonomy module gets called BEFORE subscriptions. This way you can just do a node_load and instead of getting a comma separated list of tags you would get the normal taxonomy arrays.

I'm not sure if that's entirely applicable here, but it seems related and useful.

arthurf’s picture

arthurf commented
Status: Active » Closed (fixed)

Either I've misunderstood the issue, or I've fixed it, hopefuly the later. Issue was that the free tagging taxonomies were being stored differently in the node than standard taxonomies, so i wrote a bit of code to parse them correctly and it seems to be working right.

This was fixed in the 5.0 code as well.