Hello,
I haven't found any issue to my problem so I think I might ask informations here (I hope it's the good place).
I've installed OA 2.09 ans it works quiet good for the moment exept the notifications.
What I've done:
I created users. Each user has an email.
I created Spaces. Spaces have members.
Notifications are enabled in admin/openatrium/setting
When I edit a space or section, it is written that the notifaction has been sent but I don't receive anything.
What has been tested :
Mail System has been configured here : admin/config/system/mailsystem
Site-wide default with defaultMailSystem
HTML Mail module class with HTMLMailSystem
HTML Mail module class with MimeMailSystem
Teme is Radix
When I go there : admin/config/system/htmlmail/test I can test sending emails and it works fine with all the "Test mail sending class" (default-html-mime) but not with the "testingmailsystem".
I've also tried smtp module ans I can send an email test when activating the module.
The question is why don't I receive email when asking a notifications when editing something.
Do I have to enable or configure something esle?
Thank you for your comments.
Edit : I've created a "test" user and he received the authentification mail but not notifications in a space update.
Edit2 : notifications ok in sections (tasks - news - calendar) but not in spaces. Have I missed something.....
Comment | File | Size | Author |
---|---|---|---|
#18 | oa_message_multi_notify.patch | 1.17 KB | smarchese |
#6 | OA2-Rules.png | 13.97 KB | sukh.singh |
Comments
Comment #1
pommard CreditAttribution: pommard commentedComment #2
pommard CreditAttribution: pommard commentedComment #3
mpotter CreditAttribution: mpotter commentedThe Space and Section notifications only specify the default settings for when creating new content. Only changes/creation of content within sections should send actual notification emails.
Not sure why it would say that notifications were sent since that message is set by the routine actually sending the emails. But I can check into that.
Comment #4
pommard CreditAttribution: pommard commentedOk thank you for the reply
Comment #5
sukh.singh CreditAttribution: sukh.singh commented@pommard, were you able to resolve this issue. I am having same issue as with you.
Comment #6
sukh.singh CreditAttribution: sukh.singh commentedI am able to resolve this by downloading and enabling Rules module.
Once Rules module has been install, you can view the default 3 rules by OA2.
Comment #7
mpotter CreditAttribution: mpotter commentedComment #8
Andrés Chandía CreditAttribution: Andrés Chandía commentedHi there,
in my case there were no rules at all after installing rules module, do you know if there is a place where to import the rules from?
thanks.....
Comment #9
pommard CreditAttribution: pommard commentedHi,
re-opening this issue.
Don't ask me why, but sudenly, notifications stopped working.
Everthing was working fine then we still had the green message saying the notifications were sent but didn't receive anything.
When sending a test mail via admin/config/system/htmlmail/test or admin/config/system/smtp it works fine.
Notifications are enabled, same email everywhere for the sender adress, email checked everywhere in the user settings.
So, what tells OA to use the defautmailsystem or smtp? I think something's going wrong between them two.
Does anyone had this problem?
Thank's for help
Comment #10
pommard CreditAttribution: pommard commentedComment #11
JKingsnorth CreditAttribution: JKingsnorth commentedHi pommard, is this still an issue? If so can you confirm that the mail systems are correctly set up at
admin/config/system/mailsystem
?Comment #12
pommard CreditAttribution: pommard commentedHi,
since then I've installed the 2.19 version and it works well. Maybe I had overridden to many things on the 2.09 version that made the notification bug.
On the 2.19, I use the smtpMailsystem for the sitewidedefault
++
Comment #13
JKingsnorth CreditAttribution: JKingsnorth commentedGreat, thanks pommard, this is fixed then. I'll close it immediately since it's an older version.
Comment #14
ShadowMonster CreditAttribution: ShadowMonster commentedI'm re-open this issue as I have the same problem. Emails are send normally without problems but not notifications.
Anyway in my case I found the problem. After adding some modules (do not know with make this mess) the OA_SPACE_FIELD get totally strange delta number after save, something like:
Do not have bloody idea what is messing with delta value - seams like some module do some count of something cause this number increase. Anyway cause of this function oa_messages_determine_user_notifiers can't get notifier settings cause it only relay on 0 delta value.
around line 170 of oa_messages.module of this function we have:
replacing this with:
will fix this problem.
Comment #15
mpotter CreditAttribution: mpotter commentedYou'll need to try to track down which module is messing with the delta. If the [0] delta of the og_group_ref field is not pointing to the Space of the content then a lot of other stuff in Open Atrium is going to break, not just this notification stuff. So while your above patch gets around the issue for notifications it's just a band-aid and not addressing the actual problem.
Comment #16
ShadowMonster CreditAttribution: ShadowMonster commentedYes I know that but I just want leave some track maybe someone will get sonner what make mess with delta.
Comment #17
mpotter CreditAttribution: mpotter commentedClosing this old issue. Also, "Support Requests" should never be in "Needs review" status...that is only for code patches for review.
Comment #18
smarchese CreditAttribution: smarchese commentedI'm reopening this problem because I have the same problem, emails are not sent.
I encountered the same problem described in the # 14 comment made by ShadowMonster.
Attached I send the patch that solves the indicated problem.
Comment #19
mpotter CreditAttribution: mpotter commentedPlease do not re-open old closed issues. If you have a problem and especially if you have a patch, open a new issue for it.
See comment #15 about tracking down why [0] is not the valid delta.