bug in user_activation trigger?

Next topic

Author	Message
tim tailor	Wednesday 29 September 2010 2:12:39 pm I am working on an extension for V.4.3 that creates a user content folder after the email activation. It works so far but there is some behaviour I cannot understand: The workflow is linked to the after_user_activation trigger. But this workflow is always executed two times. First when a new users registers, second when he activates his account by mail. As I am quite new to ez Publish I don't have a clue where exactly in the source I can find the code that fires the trigger. I was searching the files in kernel/user/ but I didn't have any success.
Håvard Bergersen	Monday 18 October 2010 2:22:16 pm Did you ever get a answer to this question? :)
Håvard Bergersen	Tuesday 19 October 2010 2:47:47 am I don't know if this is a bug or not, but I worked around it by checking if the user is activated or not. By doing this it doesn't do any action before the user has activated the account. :)

Author

Message

Wednesday 29 September 2010 2:12:39 pm

I am working on an extension for V.4.3 that creates a user content folder after the email activation. It works so far but there is some behaviour I cannot understand: The workflow is linked to the after_user_activation trigger. But this workflow is always executed two times. First when a new users registers, second when he activates his account by mail. As I am quite new to ez Publish I don't have a clue where exactly in the source I can find the code that fires the trigger. I was searching the files in kernel/user/ but I didn't have any success.

Håvard Bergersen

Monday 18 October 2010 2:22:16 pm

Did you ever get a answer to this question? :)

Håvard Bergersen

Tuesday 19 October 2010 2:47:47 am

I don't know if this is a bug or not, but I worked around it by checking if the user is activated or not.

By doing this it doesn't do any action before the user has activated the account. :)

eZ debug

Timing:	Jan 29 2025 14:42:13
Script start
Timing:	Jan 29 2025 14:42:13
Module start 'layout'
Timing:	Jan 29 2025 14:42:13
Module start 'content'
Timing:	Jan 29 2025 14:42:13
Module end 'content'
Timing:	Jan 29 2025 14:42:13
Script end

Main resources:

Total runtime	0.0191 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0085	588.1328	151.2109
Module start 'layout'	0.0085	0.0033	739.3438	36.6563
Module start 'content'	0.0117	0.0060	776.0000	90.0625
Module end 'content'	0.0177	0.0014	866.0625	29.9766
Script end	0.0191		896.0391

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	12.5432	14	0.0002
Check MTime	0.0011	5.8258	14	0.0001
Mysql Total
Database connection	0.0013	6.6899	1	0.0013
Mysqli_queries	0.0057	29.9320	3	0.0019
Looping result	0.0000	0.0574	1	0.0000
Template Total	0.0010	5.2	1	0.0010
Template load	0.0008	4.1686	1	0.0008
Template processing	0.0002	0.9988	1	0.0002
Override
Cache load	0.0005	2.7047	1	0.0005
General
dbfile	0.0020	10.2675	8	0.0002
String conversion	0.0000	0.0424	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs