Monday 02 June 2008 9:44:20 am - 3 replies
I'm having some trouble getting a custom content class to show up in my subtree notifications.
I have tested notifications by adding a node of class_identifier = folder to my notifications and I get notified of any updates to the node and its children so I know the notification system is working.
The problem is when I add a subtree that uses a custom content class (lets say class_identifier = my_folder) the notification email is delivered but everything is blank, no subject, no message body, even the basic stuff like the owner of the object etc.. is missing?
Do I need to add my custom classes to an ini file somewhere to include them in notifications? I have looked but can't find anywhere that this might be needed?
Also I should add that my custom classes are in their own class group, not in the content group. I feel quite stupid asking this but I have exhausted my knowledge on the issue and I can't for the life of me get custom classes to show up in notification emails...
Just so you know... Yes I cleared cache etc... I'm not a noob, but this has me completely stumped.
I'm using eZ 4.0 on:
All cronjobs are working correctly too.
Any ideas of what I might be missing?
Tuesday 03 June 2008 10:44:54 am
Well I seem to have waisted another whole day trying to figure this out...
Surely it has to be something so simple but I'm overlooking it because its just not obvious...
Does any one else have this problem running eZ 4.0? I tested on one of my 3.8 sites and there is no problem... Has something changed between 3.8 and 4.0 that would affect custom content classes in subtree notifications?
Wednesday 04 June 2008 7:33:27 am
Some ideas :
- Have you looked at the mail config ?Do you use SMTP or sendmail ? Is it properly set up ?
- Have you debugged the nottification event (I think it's in this) which has to send the mail ? have you looked at the log (ez and mail) ?
- Have tried on other content ?
Hope it helps.
Wednesday 04 June 2008 7:49:48 am
thanks for the reply, just before this notification came in I finally figured out the problem, it was a simple (but hard to spot) typo in my override ini, there was a 1 in place of a lower case l... Oops, don't know how that happened.
Funny it didn't show up in debug, but then suddenly it did...
You must be logged in to post messages in this topic!