Module result as a block

Previous topic

eZ Flow

Next topic

Author	Message
Jon Staines	Monday 19 January 2009 1:41:33 am Hi, is it possible to define a block to contain module_result.content? I've only played around with eZ Flow so far, so the answer might be right in front of me and I haven't found it yet. The default layout seems to just control the right column through the flow layout and the main part comes from the usual module_result.content call in a template. But is there a way I could control everything through the flow layout? So I could have 3 columns, a left one with a menu block (I think I can do this one) plus some other blocks beneath it, a right one with some static content and fetch block, and a central column showing the content whether it is node content OR system (user/register etc). Cheers Jon
Gaetano Giunta	Monday 19 January 2009 8:01:29 am module_result.content is 'just another var' to the pagelayout template and every other 'block template' included from it. Just try adding it 2 times in a row inside the pagelayout to see what happens. Of course it is impossible to have it from within a template that is part (or included from a template that is part) of the module_result itself. If you want flow to display menus, I think you might experiment with calling node_view_gui et/ou attribute_view_gui from within the pagelayout, pointing it to the ezflow node. Beware: the number of sql requests done per page view is likely to skyrocket (bad for scalability) Principal Consultant International Business Member of the Community Project Board
Jon Staines	Tuesday 27 January 2009 8:57:53 am Thanks. I had a chance to play around with it just now and it did seem to work. I haven't looked at menus or how it affects the load/SQL calls but I will play around with it some more.

Author

Message

Jon Staines

Monday 19 January 2009 1:41:33 am

Hi, is it possible to define a block to contain module_result.content?

I've only played around with eZ Flow so far, so the answer might be right in front of me and I haven't found it yet. The default layout seems to just control the right column through the flow layout and the main part comes from the usual module_result.content call in a template. But is there a way I could control everything through the flow layout? So I could have 3 columns, a left one with a menu block (I think I can do this one) plus some other blocks beneath it, a right one with some static content and fetch block, and a central column showing the content whether it is node content OR system (user/register etc).

Cheers
Jon

Gaetano Giunta

Monday 19 January 2009 8:01:29 am

module_result.content is 'just another var' to the pagelayout template and every other 'block template' included from it. Just try adding it 2 times in a row inside the pagelayout to see what happens.

Of course it is impossible to have it from within a template that is part (or included from a template that is part) of the module_result itself.

If you want flow to display menus, I think you might experiment with calling node_view_gui et/ou attribute_view_gui from within the pagelayout, pointing it to the ezflow node.
Beware: the number of sql requests done per page view is likely to skyrocket (bad for scalability)

Principal Consultant International Business
Member of the Community Project Board

Jon Staines

Tuesday 27 January 2009 8:57:53 am

Thanks. I had a chance to play around with it just now and it did seem to work. I haven't looked at menus or how it affects the load/SQL calls but I will play around with it some more.

eZ debug

Timing:	Jan 18 2025 04:20:46
Script start
Timing:	Jan 18 2025 04:20:46
Module start 'layout'
Timing:	Jan 18 2025 04:20:46
Module start 'content'
Timing:	Jan 18 2025 04:20:47
Module end 'content'
Timing:	Jan 18 2025 04:20:47
Script end

Main resources:

Total runtime	0.1419 sec
Peak memory usage	4,096.0000 KB
Database Queries	59

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0069	589.0625	152.6250
Module start 'layout'	0.0069	0.0046	741.6875	39.4453
Module start 'content'	0.0115	0.1289	781.1328	543.0625
Module end 'content'	0.1404	0.0015	1,324.1953	12.1563
Script end	0.1419		1,336.3516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0037	2.5764	16	0.0002
Check MTime	0.0014	1.0069	16	0.0001
Mysql Total
Database connection	0.0010	0.6997	1	0.0010
Mysqli_queries	0.0912	64.2818	59	0.0015
Looping result	0.0007	0.5172	57	0.0000
Template Total	0.0939	66.2	2	0.0470
Template load	0.0022	1.5169	2	0.0011
Template processing	0.0918	64.6451	2	0.0459
Template load and register function	0.0001	0.0753	1	0.0001
states
state_id_array	0.0017	1.1964	1	0.0017
state_identifier_array	0.0011	0.8093	2	0.0006
Override
Cache load	0.0018	1.2399	17	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.6189	2	0.0004
Fetch class attribute name	0.0021	1.4988	5	0.0004
XML
Image XML parsing	0.0009	0.6333	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0106	6	0.0000
General
dbfile	0.0008	0.5888	22	0.0000
String conversion	0.0000	0.0049	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
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	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: 15 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs