Redirecting from custom workflows

Next topic

Author	Message
Kent Wakely	Thursday 29 May 2003 9:31:26 am OK. The documentation for custom workflows says that you can have custom workflows return WORKFLOW_TYPE_STATUS_REDIRECT which will dictates the following, according to the docs: "Workflow engine should interrupt executing the workflow and redirect the user to a specified page. In case of this status the workflow event should set up some internal variables. (Will be explaned below)." The problem is, as far as I can tell, those variables are not explained below or anywhere else. So what are the variables we need to set up to allow redirection from custom workflows to work? Thanks. - kent
Selmah Maxim	Thursday 29 May 2003 9:57:02 am Hi try $RedirectUrl = "content/whatever";
Kent Wakely	Thursday 29 May 2003 10:19:34 am Tried that. Didn't work. Is that actually working for you, or was it just an educated guess? Thanks. - kent
Selmah Maxim	Thursday 29 May 2003 11:30:50 am i had tried befor, maybe i missed the spell ! i`ll check it again !
Selmah Maxim	Thursday 29 May 2003 5:10:14 pm sorry for late , i was sleepy :) here is, just test on version 3.1 , work fine for me ! $process->RedirectUrl = "/content/view/full/25"; return EZ_WORKFLOW_TYPE_STATUS_REDIRECT ;
Kent Wakely	Thursday 05 June 2003 8:49:36 am Thanks much for your help, Selmah. The problem here may be that we're running a 3.0 EZ installation (what's working for you still isn't working for me). Can someone from EZ Systems perhaps confirm that WORKFLOW_TYPE_STATUS_REDIRECT doesn't quite work right in version 3.0 (or tell me that it works fine and that the problem is with my code). Thanks. - kent

eZ debug

Timing:	Jan 18 2025 11:37:10
Script start
Timing:	Jan 18 2025 11:37:10
Module start 'layout'
Timing:	Jan 18 2025 11:37:10
Module start 'content'
Timing:	Jan 18 2025 11:37:12
Module end 'content'
Timing:	Jan 18 2025 11:37:12
Script end

Main resources:

Total runtime	1.6566 sec
Peak memory usage	4,096.0000 KB
Database Queries	66

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0091	587.9219	152.6250
Module start 'layout'	0.0091	0.0040	740.5469	39.4609
Module start 'content'	0.0131	1.6419	780.0078	498.0859
Module end 'content'	1.6550	0.0015	1,278.0938	12.1563
Script end	1.6565		1,290.2500

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0034	0.2050	16	0.0002
Check MTime	0.0014	0.0831	16	0.0001
Mysql Total
Database connection	0.0027	0.1643	1	0.0027
Mysqli_queries	1.5892	95.9333	66	0.0241
Looping result	0.0008	0.0461	64	0.0000
Template Total	1.6000	96.6	2	0.8000
Template load	0.0025	0.1518	2	0.0013
Template processing	1.5975	96.4333	2	0.7988
Template load and register function	0.0003	0.0161	1	0.0003
states
state_id_array	0.0036	0.2162	1	0.0036
state_identifier_array	0.0016	0.0957	2	0.0008
Override
Cache load	0.0020	0.1177	32	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0368	2	0.0003
Fetch class attribute name	0.0027	0.1603	6	0.0004
XML
Image XML parsing	0.0003	0.0172	2	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0009	6	0.0000
General
dbfile	0.0008	0.0496	10	0.0001
String conversion	0.0000	0.0006	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
6	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
7	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 16 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs