This site has been archived. To learn more about our current products Ibexa Content, Ibexa Experience, Ibexa Commerce head over to the Ibexa Developer Portal

eZ Community » Forums » Developer » User registration with approval workflow

User registration with approval workflow

User registration with approval workflow

Monday 31 December 2012 2:54:00 pm - 9 replies

Hi all!

I've implemented the user registration process as described here:

For approval event I have selected [Affected versions: Publishing new object]

But after editing user's object in admin user recieve an email with new activation link.

Is it possible to send verification email only once (after registering new user, not after each profile editing)?


PS I'm using Community Project 2012.8

Modified on Thursday 03 January 2013 4:44:24 pm by Sergiy Gedeon

Tuesday 01 January 2013 2:39:05 pm

Just make sure you do choose the trigger again , once you have edited the workflow

Wednesday 02 January 2013 12:17:08 pm

hmmm, this might be a bug. The solution might be to change code in the "User-approval" event type..

Thursday 03 January 2013 11:25:37 am

The only thing that the FinishUserRegister event do is:

         if( $object->attribute( 'class_identifier' ) == 'user' )
            $result = eZOperationHandler::execute( 'user', 'register', array( 'user_id' => $objectID ) );
            return $result['status'];

So there is no check for object version. Maybe user/register script contains object version validation, I'm not sure.

Thursday 03 January 2013 4:43:38 pm

PS I have installed pure ez installation with the same version (Community Project 2012.8) and confirmed that the FinishUserRegister event works bad sad.gif Emoticon

The activation email is sent each time when user is edited from backend.

Also the user receive two emails when he is activated via /user/unactivated from admin interface.

Friday 04 January 2013 12:27:38 pm

Looks really buggy to me. Further more, that harcoded "user" makes that you can only make it work with provided user class but not with other user classes you may want to create... 

Two possible solutions

  1. Indeed check version on execution
  2. Or maybe let the workflow creator the possibility or choosing if the workflow should be applied only with publishing new content. 

i would vote for 2. 

Could be a good idea add an issue on jira about... 

Modified on Friday 04 January 2013 12:29:37 pm by Carlos Revillo

Tuesday 08 January 2013 10:24:07 am

I'll report a bug soon.

BTW I found temporary solution: when we use approval by admin no email approval is needed at all. So I set VerifyUserEmail =disabled in site.ini

Monday 14 January 2013 4:17:48 pm

UPD: User still receives the registration email after editing his object from admin interface. Also I see 'Content publish cancelled' when edit user object from backend (and error message about wrong object version in debug).

The isuue in JIRA:

Modified on Monday 14 January 2013 4:39:25 pm by Sergiy Gedeon

Monday 14 January 2013 4:28:59 pm

(sorry for the late reply. Was on vacation last week).

@Sergey, maybe you can create a bug so we can work on the fix together?

Monday 28 January 2013 5:05:54 pm

Pull request:

Welcome to comment.

The frontend has version check in user/activate logic already.


You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from