Posted by mcjim on February 16, 2011 at 5:22pm
6 followers
Jump to:
| Project: | Team Notifications |
| Version: | 6.x-3.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
In notifications_team_comment(), $comment is not an object for the insert and update $op, so notifications_team_update() is always passed the same argument for $displaymsg, therefore checking or unchecking the "Do not send notifications for this update." box makes no difference and a status message will always be displayed.
This gives the impression that emails/notifications have been sent even though they haven't.
Patch attached with fix.
| Attachment | Size |
|---|---|
| notifications_team-comment-is-an-array.patch | 746 bytes |
Comments
#1
subscribe
#2
Patch in #0 works exactly as expected. RTBC.
#3
The patch in #0 is still RTBC.
Just had to apply it again after updating to Open Atrium 1.1
#4
The patch in #0 is still RTBC.
Just had to apply it again after updating to Open Atrium 1.2
#5
Indeed #0 is still good. This module hasn't got much love lately.
#6
We really appreciate everyone testing this. I'll make sure we get this rolled in soon.
#7
The patch in #0 is still RTBC.
Just had to apply it again after updating to Open Atrium 1.3
#8
Thanks! Commit 03e5416 on 6.x-2.x
#9
Thanks webflo, any chance of a new release for 6.x-2.x?
It also appears this same bug is present in the 6.x-3.x branch, if that's still being developed?
#10
I fixed the bug in 6.x-3.x and 6.x-4.x too. I roll a new release (6.x-2.1-beta9) in a few days.
#11
#12
Thanks again webflo.
#13
Automatically closed -- issue fixed for 2 weeks with no activity.
#14
Open Atrium 1.4 doesn't yet contain this patch as there hasn't been a new release of team_notifications. @webflo can you make a new release please?
#15
Sorry i was a bit late. New release is created it should be shown on the project page in a couple of hours ...
#16
No worries webflo, thank you!