I am making a site wide subscription module

Eluchel's picture

I had a need for a subscription module that would let users (anonymous or authenticated) to subscribe and receive an email when site content changed. I looked around and found a module that allowed users to subscribe to individual nodes, but I needed one that would allow a user to fill out one form and then be notified when any content on the site was updated.

So I have started to build one in my sandbox. You can see it here:
Any suggestions from others would be most appreciated.



MHz's picture

Couldn't this be accomplished using the Rules module?

Maybe, I don't have enough

Eluchel's picture

Maybe, I don't have enough experience with rules to say. I feel like what I want to do with it would be difficult to do though.
The users will have an option of how often they want to receive the email, and when that time rolls around the module will create an email that lets them know of all the updates that have happened since they last received an email.

I don't know if Rules would be able to compile that email and send it to everyone on the list. (the list would include anonymous users who subscribed)

though, If there is an easier way to do it with Rules then I am all ears!

Total Subscription module

naveenvalecha's picture

There is a total subscription module which provides functionality which would allow the user to subscribe to node pages, taxonomy terms, etc. The main feature which distinguishes it from other subscription modules is that it allows subscription for Anonymous along with Authenticated users.


Total Subscription module

Eluchel's picture

I looked at the Total Subscription module, and it just isn't quite what I want. It gave the users too many options. I just want them to be able to subscribe site wide, and maybe to subscribe to content related to a specific taxonomy term.

Message Subscribe

CK Ng | myFineJob.com

Extending vs. building

sreynen's picture

Hi Eluchel,

A few existing modules have been suggested here already, and your response in each case was that they don't provide quite the behavior you're looking for. To make the best use of Drupal, I would encourage you to look at existing modules not as potential solutions but rather as potential platforms on which to build your own solution. Good modules (which I believe includes everything mentioned here) are designed to be extensible so you're not really limited by what they do by default. Extending rather than building is a different way of thinking about modules and might be a difficult adjustment at first, but I think you'll get a lot more value out of Drupal with this approach, as you'll be focusing your efforts on the small parts that are missing rather than creating the whole solution. This may not be useful for the project you've already created, but hopefully helps in your future Drupal contributions.

That makes a lot of sense. Do

Eluchel's picture

That makes a lot of sense. Do you know any good articles that explain well the hook system?