What purpose do entries in the table 'eznotificationevent' have?

Monday 04 October 2004 5:09:22 am

I've imported a whole bunch of items and now find the table 'eznotificationevent' has grown substantially. After running cronjobs, and notifications, the table is cleared.

I've tried to look around the code and apart from finding the event created as part of the publish operation i cant find a use for it. Can i safely take out the operation call to add it in the first place?

Paul

Monday 04 October 2004 6:34:15 am

This is the thing, i dont think these entries play a part in the notification email. The entries are created when the object is published, which is independent from the main notification settings.

Is this part of the old notification system that was replaced by subtree notification?

paul

Friday 08 October 2004 4:59:01 am

bump

i dont think this a difficult question to answer.....

paul

Friday 08 October 2004 6:25:42 am

Humpty dumpty lives on!

In my db there is no subtree rule. The event is created on publish and then deleted when the job runs. But because im working with data import i've thousands of events in my db. Apart from being unnecessary the intial job run is very time consuming.

I think this is a bug but wanted someone from eZ to confirm. The notification system has changed over the years and i think this is a left over from the original system. But i could be wrong...

Look at the code in: kernel/content/operation_definition.php. At the bottom is the call to create an event while publishing something:

array( 'type' => 'method',
       'name' => 'create-notification',
       'frequency' => 'once',
       'method' => 'createNotificationEvent',
     )

If you follow this in: kernel/content/ezcontentoperationcollection.php
you will see that there is no code to check sub tree rules. It simply creates the event:

function createNotificationEvent( $objectID, $versionNum )
    {
        include_once( 'kernel/classes/notification/eznotificationevent.php' );
        $event =& eZNotificationEvent::create( 'ezpublish', array( 'object' => $objectID,
                                                                   'version' => $versionNum ) );
        $event->store();
    }

paul

Friday 08 October 2004 6:45:10 am

We only noticed it because of the cron delays ;)

I've filed it as a bug:

http://ez.no/community/bug_reports/publish_creates_unnecessary_notification_event

paul

Friday 08 October 2004 7:19:06 am

Probably ;)

At the very least i need to know if other parts of the system rely on this. So, if i remove it i wont get eZ weirdness later on...

paul

Tuesday 19 October 2004 3:31:29 am

If you do not have any notification set up, you can simply remove all entries from this table. It will not affect any other part of the system.
Back to the purpose of this table. It is general table for storing events happend in the system which can spawn sending of notification messages.