I would like to enable subscriptions to revisions of a node. The use case is that users would click "subscribe to node" and then have the choice of getting emails with 1) new comments 2) revisions to the node itself (with the log message) or selecting both.

I've written code which provides this in a separate and very specific module. I could rework it into a patch for subscriptions, but don't want to work on that unless it is desired. So, this mostly a question about whether such functionality would be a useful addition or if I should submit my module as a separate drupal.org project.

Comments

boris mann’s picture

+1 for having subscription revisions here in the subscriptions module. Great use case for wiki-style Drupal sites.

esadot’s picture

You've got my voice.

I'm looking for an ability to get notification per node's changes. Would be great if granularity could be set per content types.

brad mering’s picture

I was looking to adding exactly this functionality to the subscriptions module. I also was thinking it would be useful to move the "Subscribe to this Node" checkbox out of the edit screen, and in to the tab row at the top. I'm trying to mimic some of the look and feel of the wikipedia watchlist function.

greggles’s picture

@arthurf or @mindless - care to comment on this?

it seems popular, but your feedback is the part I desire most.

@brad mering - please don't add multiple feature requests to a single issue. For clarity we need these issues focused on one topic.

mindless’s picture

as long as you can turn on/off emails for updates in admin settings, sounds good to me.

djax80’s picture

i agree, to be able to subscribe to be informed when a nodes content is updated is what i thought this module would do...so if this could be achieved it would be great

i notice the post is a couple of months old...how would i find out if this patch has been added?

nobody1225’s picture

subscribe. +1 ,thanks

godo’s picture

Any information about this? I have tested, now, this module and this feature is not working fine.

Whith drupal 5.2:
- subscriptions-5.x-1.9.tar.gz <--- doesn't work.
- subscriptions-5.x-2.x-dev.tar.gz <--- doesn't work.

Please, I would like to know something about this.

Thanks.

greggles’s picture

@godo, note that the status is active. That means this is still just a proposal for a feature that hasn't (yet) been implemented as far as I know.

For my situation I built "yet another subscription module" because that was much faster and I hadn't heard a yes/no from the module maintainer on this idea.

godo’s picture

Thanks, greggles. If you need some "betatesters", I would like to be one of them
Meanwhile, could you share with us your "yet another subscription module"? I need to be notified when one node is updated.
I would greatly appreciate your help.

beginner’s picture

Hi,
I'm the new maintainer of notify.module, and there is the same feature request in the notify issue queue: http://drupal.org/node/150109 .
I don't want the two modules to be doing the same thing.

I mention the duplicate issue (albeit for a different module), because it is a good opportunity to clarify what each module is supposed to do.

Anyway, I won't work on this feature anytime soon for notify, because I want to deal with the bugs first: http://drupal.org/node/159427
When the bugs have been ironed out, I'll take a close look at Subscriptions to see if there is any feature overlap (inc. feature requests) and what to do about it.

salvis’s picture

OT

I'll take a close look at Subscriptions to see if there is any feature overlap (inc. feature requests) and what to do about it.

When I looked at Notify it did not support limiting notifications to specific forums, and this seems to be unchanged. This makes Notify completely unsuitable for my needs, no matter how much overlap there may be in other areas.

I don't want the two modules to be doing the same thing.

What I'm trying to say is, even if they have common functionality they are definitely not interchangeable, and it does not make sense to try to trim them down to disjoint feature sets.

I'd really like to see Notify's ability to send entire nodes (including sanitized body text) in Subscriptions though. Maybe there's a way to share code between the two modules? or even to merge them?

jamesJonas’s picture

+1

This would be a great addition to Subscriptions. Like some other posters, I had assumed that Node Changes was what subscriptions.module was created for, not that comment change notification is not also a key feature.

Node change notification is a core feature for wiki style environments. Just to add a bit of spice, I would like to see support for not only changes in the Body text, but also changes in other attributes, like location or attached image.

Node Changes subscriptions allows a community of authors to co-create a publication. When combined with Diff and Node Revisions reverting, it creates an entire social system of co-authoring of common documents.
-jj

gustav’s picture

Yes, notifications when a node is changed is important. It would be great if this could be wikipedia style: once you have been notified about one change, no notifications of further changes to the same page will be mailed to you until you visit the page. The idea is that further notifications would only clog up your inbox and are unnecessary because you already know that things have changed.

salvis’s picture

Version: 6.x-1.x-dev »
Status: Active » Fixed

Most of the ideas in this thread have been implemented in the rewrite of Subscriptions 2.0.

If you'd like to take a first look and help with testing, then get it from the link on http://drupal.org/project/subscriptions, but do heed the warnings!

salvis’s picture

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.