How pages get rendered

Next topic

Author	Message
John Hoskins	Thursday 27 March 2003 1:55:52 pm I am trying to understand how eZ Publish 3 chooses which page layout to use. So if get it right - when the request is sent to index.php. It gets the object and its section. If <yourdesign>/override/templates/ has a matching pagelayout_section_X.tpl, it is used. If <yourdesign>/templates/ has pagelayout.tpl, it is used. If those don't exist it just uses /standard/templates/pagelayout.tpl. I assume that user and admin are just other examples of templating and do not interact. So that when you look at stuff in the demo its using just the stuff in the demo or standard if it is not exist in the demo template. Thanks for all the good work, team ez.
Matthew Rat	Thursday 03 April 2003 1:14:14 pm I am having trouble figuring out how assigning a new section to your folder(s) in the admininstrative piece actually changes the look of that site. How is the section name/ID/whatever tied to some sort of page layout or such?
Karsten Jennissen	Thursday 03 April 2003 11:10:11 pm Hi, the answer on how to assign sections is here: http://ez.no/sdk/tutorials/view/permissions/ Basically, you go the the set-up section of the admin interface create the sections and then click on assign, browse folders and select to assign to that object+subfolders/objects As for the sections <-> layout, it is exactly as John said. In site.ini(.php) you specify which design folder is used for your site. You would create a new design folder for any custom site you make. First, ez publish looks for <yourdesign>/override/templates/pagelayout_section_N.tpl where N is the current section number. If not found it looks for <yourdesign>/templates/pagelayout.tpl for the general layout/css etc. If that is not found, it looks for the default design specified in the site.ini(.php). That should be "./standard/...". For more info take a look at http://ezwiki.blanko.info/index.php/Custom%20designs%20-%20directory%20structure%20explained%20%283.x%29 Karsten

Author

Message

Thursday 27 March 2003 1:55:52 pm

I am trying to understand how eZ Publish 3 chooses which page layout to use.

So if get it right - when the request is sent to index.php. It gets the object and its section.
If <yourdesign>/override/templates/ has a matching pagelayout_section_X.tpl, it is used.
If <yourdesign>/templates/ has pagelayout.tpl, it is used.
If those don't exist it just uses /standard/templates/pagelayout.tpl.

I assume that user and admin are just other examples of templating and do not interact. So that when you look at stuff in the demo its using just the stuff in the demo or standard if it is not exist in the demo template.

Thanks for all the good work, team ez.

Matthew Rat

Thursday 03 April 2003 1:14:14 pm

I am having trouble figuring out how assigning a new section to your folder(s) in the admininstrative piece actually changes the look of that site. How is the section name/ID/whatever tied to some sort of page layout or such?

Karsten Jennissen

Thursday 03 April 2003 11:10:11 pm

Hi,

the answer on how to assign sections is here:

http://ez.no/sdk/tutorials/view/permissions/

Basically, you go the the set-up section of the admin interface create the sections and then click on assign, browse folders and select to assign to that object+subfolders/objects

As for the sections <-> layout, it is exactly as John said. In site.ini(.php) you specify which design folder is used for your site. You would create a new design folder for any custom site you make. First, ez publish looks for
<yourdesign>/override/templates/pagelayout_section_N.tpl where N is the current section number. If not found it looks for <yourdesign>/templates/pagelayout.tpl for the general layout/css etc.

If that is not found, it looks for the default design specified in the site.ini(.php). That should be "./standard/...".

For more info take a look at
http://ezwiki.blanko.info/index.php/Custom%20designs%20-%20directory%20structure%20explained%20%283.x%29

Karsten

eZ debug

Timing:	Jan 18 2025 01:15:39
Script start
Timing:	Jan 18 2025 01:15:39
Module start 'layout'
Timing:	Jan 18 2025 01:15:39
Module start 'content'
Timing:	Jan 18 2025 01:15:41
Module end 'content'
Timing:	Jan 18 2025 01:15:41
Script end

Main resources:

Total runtime	1.9359 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.0046	587.9063	152.6250
Module start 'layout'	0.0046	0.0044	740.5313	39.4453
Module start 'content'	0.0090	1.9251	779.9766	504.6563
Module end 'content'	1.9341	0.0017	1,284.6328	8.1719
Script end	1.9359		1,292.8047

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	0.1834	16	0.0002
Check MTime	0.0014	0.0713	16	0.0001
Mysql Total
Database connection	0.0006	0.0298	1	0.0006
Mysqli_queries	1.8843	97.3326	59	0.0319
Looping result	0.0008	0.0395	57	0.0000
Template Total	1.8874	97.5	2	0.9437
Template load	0.0020	0.1020	2	0.0010
Template processing	1.8854	97.3926	2	0.9427
Template load and register function	0.0002	0.0090	1	0.0002
states
state_id_array	0.0021	0.1071	1	0.0021
state_identifier_array	0.0024	0.1247	2	0.0012
Override
Cache load	0.0016	0.0824	23	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.0475	3	0.0003
Fetch class attribute name	0.0012	0.0610	3	0.0004
XML
Image XML parsing	0.0004	0.0200	3	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0006	3	0.0000
General
dbfile	0.0011	0.0582	10	0.0001
String conversion	0.0000	0.0004	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/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	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: 14 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs