Triggers and workflow: too limited now

Previous topic

Suggestions

Next topic

Author	Message
Paul Borgermans	Tuesday 01 July 2003 9:48:29 am Hello, Maybe I missed some essentials about workflows/triggers (being an absolute beginner on this), mainly when and where they are executed: - triggers are used per module/function, no way to discriminate between different parts of your site (be it sections, node trees, ...), it appears one should do this in the workflow => I think it would be much more logical and powerful to select sections/nodetrees and classes with the triggers ("create new trigger for section a if an object of class b is created by user c"). - to handle different parts differently (sounds logical?), you you should filter with the multiplexer event type which is limited to sections and classes (however, failed to do this in 3.1 for even launchhing a one event workflow, maybe a bug, not sure yet) => This creates a huge super-workflow which contains all the different workflows for different (unrelated) functionalities. Somehow, I feel/think triggers are in the wrong place when they are limited to global module/actions (pre and post). Any thoughts from more experienced people on this matter? --paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans

Author

Message

Paul Borgermans

Tuesday 01 July 2003 9:48:29 am

Hello,

Maybe I missed some essentials about workflows/triggers (being an absolute beginner on this), mainly when and where they are executed:

- triggers are used per module/function, no way to discriminate between different parts of your site (be it sections, node trees, ...), it appears one should do this in the workflow

=> I think it would be much more logical and powerful to select sections/nodetrees and classes with the triggers ("create new trigger for section a if an object of class b is created by user c").

- to handle different parts differently (sounds logical?), you you should filter with the multiplexer event type which is limited to sections and classes (however, failed to do this in 3.1 for even launchhing a one event workflow, maybe a bug, not sure yet)

=> This creates a huge super-workflow which contains all the different workflows for different (unrelated) functionalities.

Somehow, I feel/think triggers are in the wrong place when they are limited to global module/actions (pre and post).

Any thoughts from more experienced people on this matter?

--paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

eZ debug

Timing:	Jan 18 2025 10:35:03
Script start
Timing:	Jan 18 2025 10:35:03
Module start 'layout'
Timing:	Jan 18 2025 10:35:03
Module start 'content'
Timing:	Jan 18 2025 10:35:04
Module end 'content'
Timing:	Jan 18 2025 10:35:04
Script end

Main resources:

Total runtime	0.8353 sec
Peak memory usage	4,096.0000 KB
Database Queries	46

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0055	589.1484	152.6406
Module start 'layout'	0.0056	0.0027	741.7891	39.4766
Module start 'content'	0.0082	0.8255	781.2656	469.5313
Module end 'content'	0.8337	0.0016	1,250.7969	8.1406
Script end	0.8352		1,258.9375

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.3957	16	0.0002
Check MTime	0.0013	0.1596	16	0.0001
Mysql Total
Database connection	0.0008	0.1005	1	0.0008
Mysqli_queries	0.7916	94.7669	46	0.0172
Looping result	0.0004	0.0508	44	0.0000
Template Total	0.8028	96.1	2	0.4014
Template load	0.0023	0.2697	2	0.0011
Template processing	0.8006	95.8454	2	0.4003
Template load and register function	0.0001	0.0132	1	0.0001
states
state_id_array	0.0009	0.1082	1	0.0009
state_identifier_array	0.0013	0.1609	2	0.0007
Override
Cache load	0.0018	0.2134	13	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0008	0.1000	1	0.0008
Fetch class attribute name	0.0016	0.1859	2	0.0008
XML
Image XML parsing	0.0005	0.0576	1	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0003	2	0.0000
General
dbfile	0.0009	0.1043	17	0.0001
String conversion	0.0000	0.0039	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
1	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 5 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs