On which web page are nodes published?

Next topic

Author	Message
Jozef Baum	Monday 22 June 2009 3:33:17 pm I am new to eZ Publish. I have already read a large part of the technical manual for eZ Publish 4.0 (the Reference is still not complete, and there is not yet a manual for eZ Publish 4.1; furthermore, I wonder if users with a commercial license get documentation about how building a site, besides the article about it in the old documentation of eZ Publish, and if they get documentation that is better structured and written in somewhat more decent English). I have read about sections, content objects, nodes, and the node tree. But can someone please tell me how I will have to specify which nodes with their content object will be published on which web page of my website? In other words, which notion in eZ Publish corresponds to a single web page? Thank you in advance.
André R.	Tuesday 23 June 2009 2:49:56 am "and there is not yet a manual for eZ Publish 4.1" 4.0 doc is supposed to become 4.x doc and just mention the new things inline like the php doc does. We have hired some new technical writers lately, so hopefully someone will work on the doc again. "furthermore, I wonder if users with a commercial license get documentation about how building a site" There is no off line documentation, its the normal doc: http://ez.no/doc/ez_publish/technical_manual/4_0 old doc: http://ez.no/ezpublish/documentation/toc community wiki: http://ezpedia.org/ and api doc/svn links/external links: http://pubsvn.ez.no/ "which nodes with their content object will be published on which web page of my website? In other words, which notion in eZ Publish corresponds to a single web page?" eZ Publish is single site out of the box(a translation does not count as a separate site, even though it requires a separate 'siteaccess' in eZ Publish), if you want to host several sites on same db, then you need to: 1. create several root folders in the content tree, so the entry point of the webpage moves one level up 2. (optional) change site.ini [SiteAccessSettings] setup to be host based and not url based 3. change a few settings (content ini rootNode and optionally site.ini PathPrefix & PathPrefixExclude) 4. modify some pagelayout related templates so they show the correct path, menu and so on. There are other more detailed guides on 'multi site setup' around in the forum, but this should get you started. When you have done point one, then it becomes very clear witch webpage content goes to when you publish new content. Since you always needs to pick location first in eZ Publish ;) eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom

Author

Message

Monday 22 June 2009 3:33:17 pm

I am new to eZ Publish.

I have already read a large part of the technical manual for eZ Publish 4.0 (the Reference is still not complete, and there is not yet a manual for eZ Publish 4.1; furthermore, I wonder if users with a commercial license get documentation about how building a site, besides the article about it in the old documentation of eZ Publish, and if they get documentation that is better structured and written in somewhat more decent English).

I have read about sections, content objects, nodes, and the node tree. But can someone please tell me how I will have to specify which nodes with their content object will be published on which web page of my website? In other words, which notion in eZ Publish corresponds to a single web page?

Thank you in advance.

André R.

Tuesday 23 June 2009 2:49:56 am

"and there is not yet a manual for eZ Publish 4.1"
4.0 doc is supposed to become 4.x doc and just mention the new things inline like the php doc does. We have hired some new technical writers lately, so hopefully someone will work on the doc again.

"furthermore, I wonder if users with a commercial license get documentation about how building a site"

There is no off line documentation, its the normal doc:
http://ez.no/doc/ez_publish/technical_manual/4_0

old doc:
http://ez.no/ezpublish/documentation/toc

community wiki:
http://ezpedia.org/

and api doc/svn links/external links:
http://pubsvn.ez.no/

"which nodes with their content object will be published on which web page of my website? In other words, which notion in eZ Publish corresponds to a single web page?"

eZ Publish is single site out of the box(a translation does not count as a separate site, even though it requires a separate 'siteaccess' in eZ Publish), if you want to host several sites on same db, then you need to:

1. create several root folders in the content tree, so the entry point of the webpage moves one level up
2. (optional) change site.ini [SiteAccessSettings] setup to be host based and not url based
3. change a few settings (content ini rootNode and optionally site.ini PathPrefix & PathPrefixExclude)
4. modify some pagelayout related templates so they show the correct path, menu and so on.

There are other more detailed guides on 'multi site setup' around in the forum, but this should get you started. When you have done point one, then it becomes very clear witch webpage content goes to when you publish new content. Since you always needs to pick location first in eZ Publish ;)

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

eZ debug

Timing:	Jan 18 2025 22:27:32
Script start
Timing:	Jan 18 2025 22:27:33
Module start 'layout'
Timing:	Jan 18 2025 22:27:33
Module start 'content'
Timing:	Jan 18 2025 22:27:33
Module end 'content'
Timing:	Jan 18 2025 22:27:33
Script end

Main resources:

Total runtime	0.8196 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0071	589.1484	152.6406
Module start 'layout'	0.0071	0.0032	741.7891	39.4766
Module start 'content'	0.0103	0.8078	781.2656	534.4844
Module end 'content'	0.8181	0.0014	1,315.7500	12.1406
Script end	0.8196		1,327.8906

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0036	0.4434	16	0.0002
Check MTime	0.0015	0.1785	16	0.0001
Mysql Total
Database connection	0.0008	0.0965	1	0.0008
Mysqli_queries	0.7699	93.9357	54	0.0143
Looping result	0.0007	0.0794	52	0.0000
Template Total	0.7848	95.8	2	0.3924
Template load	0.0022	0.2722	2	0.0011
Template processing	0.7826	95.4814	2	0.3913
Template load and register function	0.0003	0.0331	1	0.0003
states
state_id_array	0.0007	0.0827	1	0.0007
state_identifier_array	0.0015	0.1877	2	0.0008
Override
Cache load	0.0019	0.2302	27	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0742	2	0.0003
Fetch class attribute name	0.0011	0.1292	3	0.0004
XML
Image XML parsing	0.0006	0.0680	2	0.0003
class_abstraction
Instantiating content class attribute	0.0000	0.0009	3	0.0000
General
dbfile	0.0007	0.0887	17	0.0000
String conversion	0.0000	0.0011	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
2	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/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
6	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: 18 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs