Closed (won't fix)
Project:
Notifications
Version:
6.x-4.x-dev
Component:
Notifications
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Nov 2010 at 15:58 UTC
Updated:
3 Feb 2012 at 15:27 UTC
I almost spent the last 3 days figuring out why Notifications wasn't working on my Drupal installation 6.19.
There is what happens.
When I set up a TRIGGERED RULE with the Rules module to perform an action on "After saving content" --> Notifications are not queued (and not sent of course).
My first guess is that the RULE override the notification process after a user create a new content.
I tested with Notifications 2.3 and 4.x-dev.
I tested on a CLEAN install.
I'm ready to provide any information to maintainers in order to help in solving the problem.
Comments
Comment #1
titi88888888 commentedI thought I could explain how I managed to make a work around this problem.
This doesn't mean the problem is Fixed.
The idea is to Give a priority to Notifications over Rules.
I installed the module "Module Weight" from the "UTIL" modules package, and gave a priority of :
- 20 to "content notification" module
- 50 to "Rules" module.
This way, the Notifications are triggered before the rules, which works fine.
Hope this could help !
Comment #2
jose reyero commentedLooks to me like Rules module issue.
Comment #3
caw67 commentedyou are my hero!
have had the same problem and tried with scheduled rules ( 2 minutes after saving content via cron), but not ver good.
your solution works great (with util and module weight!)