Currently receiving a bunch of notifications as a result of the recent GDO upgrade. This is awesome. However it's hard to discern what's what, because the subject gives no indication of the forum or group.
I suggest that, as with issue queue updates, we include the forum or group name as a prefix to the notification.
It may be that this is the intended functionality but it's not working as planned. For example, I'm subscribed to group CiviCRM but not group Boston. I received a notification for this job posting but the subject of the email was groups.drupal.org Boston: Drupal + CiviCRM config guru | 53 Technology.
I believe the subject should read groups.drupal.org CiviCRM: Drupal + CiviCRM config guru | 53 Technology
Either that post was placed in a group named "Boston" as well, and my subscription notified me but selected the incorrect group name to prefix the notification with, or ... or something else wierd happened.
Comments
Comment #1
gábor hojtsy@xurizaemon: the post was put in the Boston, CiviCRM, New Hampshire and Vermont groups.
BTW same issue was reported on a localize.drupal.org post (similar og + og_notifications setup), where the post was put into multiple groups. See comments on http://localize.drupal.org/node/264
Comment #2
xurizaemonThanks Gábor.
Also noting that while notifications sent immediately contain a group prefix (which may be incorrect as above), digest notifications do not show any indication of the group(s) which the message contains updates for. A daily digest appears to contain updates for multiple groups, so this might need to happen per-message in the digest. This is probably worth a separate feature request, unless it's a trivial modification to the notifications template, which appears to be producing repetitive emails if there are +1 comments on a node (?)
Eg, the most recent digest email I received contains what I think should render simply as (note I've added group subjects)
But actually I received (nine repetitions of one comment URL and two of the other):
Comment #3
gregglesThis is really a notifications (or maybe og_notifications) issue.