Forums / Developer / Notitications not working

Notitications not working

Author Message

Clive Flatau

Thursday 03 February 2005 6:00:45 am

I just want to get notifications for adding content to a subtree - which I set up for example by using the admin interface My Account/My Notification settings/Notifications.

I select the subtree I'm interested in. Publish an e-mail there and don't get a notification. The email config is ok (i.e.

[TransportSettings]
DefaultTransport=SMTP

[MailSettings]
Transport=SMTP
TransportServer=my.smtp.server.com
TransportUser=
TransportPassword=
[email protected]
[email protected]

And this works for user registration.

Any ideas please?

Frederik Holljen

Thursday 03 February 2005 6:10:44 am

My guess is that you have forgotten to set up the cronjob that does the actual notification work: http://ez.no/ez_publish/documentation/installation/the_cronjob_script

Clive Flatau

Thursday 03 February 2005 6:23:30 am

I should have added that I am running the runcronjobs.php script and I can see the event appear in eznotiticationevent and being cleared after the event is run. Also I can see the rule in ezsubtree_notification_rule for the correct user id.

Any more ideas anyone?

Eivind Marienborg

Thursday 03 February 2005 10:01:24 am

I had lots of trouble setting up notifications.. What solved my problems was making sure that I had specified which cronjobs to actually run (in override/cronjob.ini.append), and setting up the cronjob-table. This might be a clue.

Clive Flatau

Thursday 03 February 2005 10:06:05 am

I know it's running the cronjob because I'm running the script on a windows system (for development) amd I run it by command-line with the following results:

Running cronjobs/workflow.php
Checking for workflow processes
Status list

0 out of 0 processes was finished

Running cronjobs/notification.php
Starting notification event processing
Done

Running cronjobs/unpublish.php

Running cronjobs/indexcontent.php
Starting processing pending search engine modifications
Done

As mentioned in my previous post I see the event added to the db table, so it must to do with the sending process.