Tuesday 08 June 2004 4:46:10 am

Hi paul, thanx for the swift reply.

Could you perhaps explain in more detail how to go about it using the notification module?

The site is an online magazine. When a new issue is published, the homepage should be sent to all newsletter subscribers, but not necessarily at the same time the homepage is published. The editor should also be able to 'manage' the subscribers: add and remove them manually for instance?

thanx again
rinze

Wednesday 09 June 2004 3:06:34 am

Hi sebastian!

I'll try to implement it using the information given. When (if) i run into problems, i'll try and contact you through the forum!

thanx for the help, i should get this to work!

Wednesday 09 June 2004 3:57:08 am

Use phplist http://tincan.co.uk/phplist

It works quite well

bjoern
-
http://www.xrow.de

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Wednesday 09 June 2004 9:05:53 am

Yes, when both kinds of users have the same content class the trigger will start the script unwanted. But perhaps the two user differ in some attributes, so you can let the script decide if notification is set or not. To read the attributes of an object is not difficult.

The script has to be written by you, you have to create a new Event. If you like, perhaps I could post or mail my source. But therefore I have to ask a colleage to post the code because I'm not working on eZ any more. This couldn't be done bevore friday, on thursday there is holiday in germany.

Contact me on this forum if I could help you further more.

Monday 14 June 2004 12:27:09 am

Hi Rinze,

this is the code snippet from Sebastian's event type.

...
function execute( &$process, &$event ) 
{
    eZDebug::writeNotice("Start","Workflow clubapplication");
		
    // get object and object id
    $parameters = $process->attribute( 'parameter_list' );
    $object =& eZContentObject::fetch( $parameters['object_id'] );
    $objectId= $parameters['object_id'];
		
    // add user to newsletter-notification Folder "Community-Newsletter" NodeID 1177
    include_once( 'kernel/classes/notification/handler/ezsubtree/ezsubtreenotificationrule.php' );
    $nodeIDList =& eZSubtreeNotificationRule::fetchNodesForUserID( $objectId, false );
    $nodeID = 1177;
    if ( !in_array( $nodeID, $nodeIDList ) ) 
    {
	eZDebug::writeNotice("NotificationRule","Workflow clubapplication");
	$rule =& eZSubtreeNotificationRule::create( $nodeID, $objectId );
	$rule->store();
    }
}
...

In our example this event is set up as multiplexer for content class "User", trigger is "content create after".
Users are able to modify their "newsletter" settings within the notification settings (/notfication/settings).
What is still missing for you is that editors can handle other user's notification settings. No idea if anybody already worked on this.

hth
Silke

Tuesday 15 June 2004 4:27:19 am

It was almost complete... just missing the default event stuff.

<?php

define( "EZ_WORKFLOW_TYPE_CLUBAPPLICATION_ID", "clubapplication" );
include_once("kernel/classes/ezworkflowtype.php");

class clubapplicationtype extends eZWorkflowEventType
{
    function clubapplicationtype() 
    {
        $this->eZWorkflowEventType( EZ_WORKFLOW_TYPE_CLUBAPPLICATION_ID, "Club Application" );
    }

    function execute( &$process, &$event ) 
    {
	eZDebug::writeNotice("Start","Workflow clubapplication");
	
	// see last posting...

    }	
}

eZWorkflowEventType::registerType( EZ_WORKFLOW_TYPE_CLUBAPPLICATION_ID, "clubapplicationtype" );

?>

The function "execute" defines what that event actually does.
If you want to rename the event type, you have to change the first and last line (define and registerType) and the class name. And take care of directory structure.

See also http://ez.no/ez_publish/documentation/development/extensions/workflow_events/creating_a_new_event
and the wrapping event as example
http://ez.no/ez_publish/documentation/development/extensions/workflow_events/wrapping_event

Good luck,
Silke

Wednesday 16 June 2004 5:39:58 am

Rinze,

i updated my old 3.3-1 version to 3.3-5 (and then 3.4-0)
using the 3.3-5 i noticed that notification works!
But i saw some difference between 3.4-0 with installer and 3.4-0 'upgraded', so this can be the problem

i'm very interested to what you are trying to do (implementing a mailing list where an administrator can subscribe other users. )
see http://ez.no/community/forum/setup_design/new_notification_type_needed_help

hope we can work togheter
icq # 326-457-502

best regards to all
alessandro

Thursday 17 June 2004 3:46:22 am

Hi Rinze!

Have you set up the eZ- and the Linux-cronjobs properly?
(e.g. see http://ez.no/ez_publish/documentation/configuration/configuration/cron_jobs)

Sebastian

Monday 21 June 2004 2:17:39 am

Hi guys,

Notifications are functioning, so I started implementing the code presented above. I have two questions:

1. from the code I can't see the relation to the 'create user event'? The following sentence probably explains this, but I simply don't understand! Can't find any documentation on the multiplexer for that matter!
<"In our example this event is set up as multiplexer for content class "User",>

So I guess my first question is, how do I do this?

2. Secondly, if I were to send the newsletter, would it be possible to isolate the rule for the newsletter? Using the execute notification filter from the admin interface executes all rules available.

sorry for the great load of questions, i am really trying to understand the notification and event system.

@allesandro: i'll have to create an icq account first. I'll contact you later?

Monday 21 June 2004 2:52:48 am

hi allesandro,

the site administrator should be able to add and remove subscribers for the newsletter.

greetz
rinze