Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The old subscriptions module in d4.7 allowed you to subscribe to the node that you were creating. We required this for d6 and the notifications_autosubscribe module seemed the place where this functionality should be placed.
The attached patch provides that functionality for the module and also brings up the module to the d6 code standard since some of this module still utilizes the d5 way for form alter etc.
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | notifications_autosubscribe.module.patch | 2.93 KB | darren.ferguson |
| notifications_autosubscribe.module.patch | 3.52 KB | darren.ferguson |
Comments
Comment #1
geodaniel commentedComment #2
geodaniel commentedSee also #252350: drupal 6 port of notifications_autosubscribe module, on which I've noted that this patch has an additional feature, so this is perhaps the one to focus on. Darren, what do you think?
Comment #3
darren.ferguson commentedThey are using autosubscribe as a check box to automatically subscribe to the content. Kind of misleading since really you would be subscribing, if autosubscribing the system should do that automatically for the user. I think our patch does the same except we have subscribe button and utilize subscription on the thread basis for the node, or other type. In theirs i think it would turn on autosubscribe for that type but i am not 100% sure it is just how i read it.
Comment #4
jose reyero commentedThe module seems to be updated, I really don't remember when, so this no longer applies.
I may be missing something here, reopen if so.
Comment #5
darren.ferguson commentedI think we look good on it now, thanks
Comment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #7
darren.ferguson commentedJose
Re-opened this with the patch that adheres to the user settings for autosubscribing.
The patch adds this functionality to let the user subscribe to content in their profile so that they can determine if they wish to autosubscribe.
If they check they want too then this change will never be displayed. If they do not click it, the autosubscribe check box is displayed but not checked and the user can then check against it.
Comment #8
jose reyero commentedHey Darren,
Looks like you're up to something but I don't really get the full extent of this patch. You mean we use the autosubscribe setting for populating the default value of the check box?
There are a few things also, like replacing current hooks (?), what happens with comments (?), the fieldset (we are standardizing on a 'notifications' fieldset so all the modules adding notifications options to the search form can group them there....
Anyway, I agree the whole autosubscribe feature is kind of incomplete and not really intuitive so there's a lot of room for improvement here. I'd just need to have the whole picture outlined a bit better.
Comment #9
jose reyero commentedClosing since no follow up.