mahara-contributors team mailing list archive
-
mahara-contributors team
-
Mailing list archive
-
Message #09393
[Bug 1009301] A change has been merged
Reviewed: https://reviews.mahara.org/1303
Committed: http://gitorious.org/mahara/mahara/commit/8826dbf0e50e838b6e400393167377aefeee7690
Submitter: Hugh Davenport (hugh@xxxxxxxxxxxxxxx)
Branch: master
commit 8826dbf0e50e838b6e400393167377aefeee7690
Author: Richard Mansfield <richard.mansfield@xxxxxxxxxxxxxxx>
Date: Wed Jun 6 14:45:37 2012 +1200
Don't recursively notify admins about notification exceptions (bug #1009301)
Avoid stupid attempts to notify admins about failed notifications when
we're in the middle of notifying the admins about failed
notifications.
Change-Id: I50037d93e3caf32e8de116cbd638fe5563957ce1
Signed-off-by: Richard Mansfield <richard.mansfield@xxxxxxxxxxxxxxx>
--
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/1009301
Title:
Too many admin notifications about notification failures
Status in Mahara ePortfolio:
Fix Committed
Bug description:
When a notification method throws an exception, Mahara tries to notify
all the site admins to warn them that a "User notification error was
probably caused by your server configuration."
This can fill up the notification_internal_activity table. The number
of these messages can be reduced by not trying to notify the admins
when the admin notification itself fails, and by sending them once
only per cron run.
See https://mahara.org/interaction/forum/topic.php?id=3829 and
https://mahara.org/interaction/forum/topic.php?id=4578
To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1009301/+subscriptions
References