Will notifications 2.1 work for OG 1.3
idcm - August 16, 2009 - 21:19
| Project: | Notifications |
| Version: | 6.x-1.1 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | ScottBaetz |
| Status: | closed |
Jump to:
Description
I saw on the project page that if you have OG 1.3, that notifications 1.1 will work. Does that mean 2.1 won't work?
I have actually tried both and neither send out notices when someone posts to the group. I have read over the messages in the issue gueue but until I know which version I have to use for OG1.3, I don't know if this issue is a duplicate.
At the moment I have notifications 1.1 installed. If I have the feature set to send copy to person who made the post, the copy of the message comes thru. But if that is not set, no messages come thru.
Is there a better version for OG1.3?
please help ASAP
thanks
c
#1
Doesn't it just drive you CRAZY how no one answers these basic questions. I'm in the same situation, although I think I've figured out why (there's a missing function some where) but still no help for me either!
UGH.
#2
Ok..
So, here's the KEY to my own situation. The answer is yes, but YOU MUST insure that you've double, triple checked the module version releases. I was struggling for a few days, reading error logs, when suddenly I realized, screaming before my own eyes, that I was using the Messaging Module Release 6.x 1.0 UGH.. needed 6.x 1.1
Then I had to download the PHPMailer class phew..
Now everything works perfect!
#3
thank you!! I have a client that needs notifications 2.x so this really helps.
c
#4
SOLUTION....
So, here's the KEY to my own situation. The answer is yes, these will work. YOU MUST insure that you've double, triple checked the module version releases. I was struggling for a few days, reading error logs, when suddenly I realized, screaming before my own eyes, that I was using the Messaging Module Release 6.x 1.0 UGH.. needed 6.x 1.1
Then I had to download the PHPMailer class phew..
Now everything works perfect!
#5
Automatically closed -- issue fixed for 2 weeks with no activity.