Directly publish after validation

Previous topic

Setup & design

Next topic

Author	Message
Damien MARTIN	Thursday 01 April 2010 5:59:23 am Hi there, I would like to know if it is possible to skip the workflow process to allow contents to be published directly after being validated. Contents are validated using a standard worflow process. So, for the moment, contents are waiting for approval after their creation. The workflow is running via runcronjobs.php, going in "my account" for approval, next, it is approved and waits for the cronjob to be executed to finaly be published. But it is too long... 1min is too long... So, can I skip the process after validation to publish directly ? Thanks, Damien

Author

Message

Damien MARTIN

Thursday 01 April 2010 5:59:23 am

Hi there,

I would like to know if it is possible to skip the workflow process to allow contents to be published directly after being validated.

Contents are validated using a standard worflow process. So, for the moment, contents are waiting for approval after their creation. The workflow is running via runcronjobs.php, going in "my account" for approval, next, it is approved and waits for the cronjob to be executed to finaly be published.

But it is too long...

1min is too long...

So, can I skip the process after validation to publish directly ?

Thanks,

Damien

eZ debug

Timing:	Jan 18 2025 01:03:59
Script start
Timing:	Jan 18 2025 01:03:59
Module start 'layout'
Timing:	Jan 18 2025 01:03:59
Module start 'content'
Timing:	Jan 18 2025 01:04:00
Module end 'content'
Timing:	Jan 18 2025 01:04:00
Script end

Main resources:

Total runtime	0.7525 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.0045	590.8828	152.6250
Module start 'layout'	0.0045	0.0029	743.5078	39.4453
Module start 'content'	0.0074	0.7436	782.9531	431.7422
Module end 'content'	0.7510	0.0015	1,214.6953	8.1563
Script end	0.7525		1,222.8516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.3926	16	0.0002
Check MTime	0.0012	0.1588	16	0.0001
Mysql Total
Database connection	0.0007	0.0911	1	0.0007
Mysqli_queries	0.7168	95.2523	46	0.0156
Looping result	0.0004	0.0489	44	0.0000
Template Total	0.7261	96.5	2	0.3630
Template load	0.0018	0.2357	2	0.0009
Template processing	0.7243	96.2447	2	0.3621
Template load and register function	0.0001	0.0104	1	0.0001
states
state_id_array	0.0008	0.1007	1	0.0008
state_identifier_array	0.0012	0.1538	2	0.0006
Override
Cache load	0.0014	0.1837	12	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0654	1	0.0005
Fetch class attribute name	0.0007	0.0978	2	0.0004
XML
Image XML parsing	0.0003	0.0446	1	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0006	2	0.0000
General
dbfile	0.0011	0.1500	16	0.0001
String conversion	0.0000	0.0008	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