Email notification as a daily digest
| Project: | Organic groups |
| Version: | HEAD |
| Component: | og.module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | moshe weitzman |
| Status: | won't fix |
Jump to:
I think it would be really useful for group subscribers to be able to receive email notifications as "daily digests".
In high-traffic groups, it soon becomes impractical to keep track of posts by "one-email-per-post" notification, because of the flood of emails that are generated. This is especially true for webmail users, or those without the skill or inclination to set up folders to filter their mail. It is a frequent request on the site I am running.
The feature could be integrated into the interface simply by adding a checkbox to the "my settings" page.
Unfortunately I don't have the time or skills (I think) to add this feature myself, but if it could be added to a "todo" list, that would be fantastic.

#1
i have some prototype code for a maildigest.module which is in contrib CVS right now. not quite ready yet. can digestify any mailings you want, not just og mailings.
#2
hope it works with notify module too. (sounds like your intention is broad - which is GOOD). count me in as a tester... is it ready for that?
#3
Ah, that's sounds great. I'd be happy to do some testing.
#4
Daily digest would be ideal! (subscribed)
#5
Subscribing to this new feature.
#6
I'm interested in this feature. Happy to test. I see nothing has happened to http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/maildigest/... for since May. Do you expect to do any further work on it? If not, do you have any advice for anyone considering progressing the development?
#7
subscribing
#8
i am not working on maildigest, so i hope someone else takes the reins.
#9
I'd like to see that feature, too.
#10
please see the nascent maildigest module (http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/maildigest/) and work on it as needed. or start a new digest module ... i'm not planning an OG specific digest.
#11
Is maildigest working?
#12
I am taking a look and at the above code and there is a good chance I'll finish it or rewrite my own as I desperately need this feature. So if anyone else happens to come upon this thread, that's the latest news.
#13
I'll be behind you, rooting for and testing your code if you do any work for it.
#14
Me too, this is an absolute must! Good luck!
#15
Is there a drupal project for this maildigest module yet where its development is being discussed?
#16
Nope. The only thing that now exists is the stuff from the link above. I'll hopefully have time Thursday or Friday to begin working on this. Once I get a semi-working version done, I'll create a project and open a discussion thread in the issue queue. I haven't looked to see how in/complete the module is in its current condition. I hope Moshe gave us a good start.
And for anyone interested, I have produced a few OG-related modules that I think are pretty cool; so check them out.
#17
thanks rconstantine. you actually want to ignore the latest commit on that module and instead use the one before (http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/maildigest/...).
i was coerced by a client to move the module in a not so good direction in that last commit.
#18
rconstantine, thank you very much for working on the digest feature. Could you write the module in such a way that it plugs in nicely to the subscription module (drupal.org/project/subscription)? That module has just been rewritten in such a way that it should be easy to plug in the digest feature.
#19
I'll look at the subscription module, but won't make any promises at this point. I'm sure you can understand.
Thanks Moshe!
#20
Oh, Moshe, what about the install file? I see you removed a column. Without looking at your code, I would guess that you replaced the sent column with entries to watchdog. Would that be correct?
Also, would you mind giving me a brief overview of where you began in the design and where you thought it might go? Thanks.
#21
use the prior version of .install too.
the intent of the module is to intercept outbound emails and queue them to a DB. not every email, just those whose mailkeys are specified by the admin. so the admin could queue og notifications and other mailings but not password reminders, for example, during cron, maildigest looks and see if any of the recipients are due for their digest. if so, it sends them all the mail thats waiting for them in the queue.
#22
Thanks. I'm finishing up two things then will be getting to this. I hope to have it done by mid-January.
#23
How does this compare to the Subscription module's digest feature? It seems we could combine efforts here.
#24
Subscription, or Subscriptions? The former has not been updated for 5.x I notice, but the latter has recently undergone a total rewrite and is nearly finished with its 2.0 beta testing. I have not evaluated the features of each to determine which you are talking about. However, combining efforts is always a good idea. I'm finally starting on this later today.
#25
It is the subscriptions module that has the digest feature. It does not yet integrated with the organic groups module, but see http://drupal.org/project/subscriptions_og.
rconstantine: Did you get the message I sent via your drupal contact form?
#26
so, what's my best bet as of now if I have a site using organic groups, and want simple digest functionality? Seems like there are several options, but they're all in development. Which is the most stable and feature complete?
#27
@gustav, yep. I was going to get to it today.
#28
since we are likely going to integrate with subscriptions or notifications modules, i don't think we need to focus on this issue anymore. both of those frameworks already have digest mode.
#29
Agreed. As noted elsewhere, I will see if there is anything I can contribute to one of the existing efforts. Thanks anyway moshe for the starting code!
#30
subscibing
#31
Very interested in this project - any movement?
#32
I'm interested in this as well, but am hoping that the OG notifications integration will provide this functionality
Seems like something that should NOT be handled in OG core