how to use sections?

Next topic

Author	Message
Luis FLores	Monday 27 December 2004 10:04:45 am Hi, I am new to eZpublish, I justs installed 3.5 without problems. I will like to know how to use Sections, is it possible to use sections to separate different sites? I will like to have two sites on the same instalation, possible each one wih a different root folder. Should I use sections? or any other way? Thanks
Valenti salas	Friday 31 December 2004 2:43:55 am Hi, As I know, sections are used to separate the content in diferent conceptual areas and then apply some rules (for example templates) to all the objects in a section . I your templates you can check the section of the node or the nodes that you recive in a fetch function and do some with the information. Sections are a way to organize your content in diferent areas with nodes that have to be similar. To use diferent sites on the same installation you have to search in documentation by 'siteaccess'. Normally you have to create one siteaccess for any site you have to do. I think that is posible to specify a diferent root folder location using de config files (maybe the site.ini.append of each siteaccess). Valenti.

Author

Message

Monday 27 December 2004 10:04:45 am

Hi,

I am new to eZpublish, I justs installed 3.5 without problems. I will like to know how to use Sections, is it possible to use sections to separate different sites?

I will like to have two sites on the same instalation, possible each one wih a different root folder. Should I use sections? or any other way?

Thanks

Valenti salas

Friday 31 December 2004 2:43:55 am

Hi,

As I know, sections are used to separate the content in diferent conceptual areas and then apply some rules (for example templates) to all the objects in a section . I your templates you can check the section of the node or the nodes that you recive in a fetch function and do some with the information. Sections are a way to organize your content in diferent areas with nodes that have to be similar.

To use diferent sites on the same installation you have to search in documentation by 'siteaccess'. Normally you have to create one siteaccess for any site you have to do. I think that is posible to specify a diferent root folder location using de config files (maybe the site.ini.append of each siteaccess).

Valenti.

eZ debug

Timing:	Jan 19 2025 00:11:33
Script start
Timing:	Jan 19 2025 00:11:33
Module start 'layout'
Timing:	Jan 19 2025 00:11:33
Module start 'content'
Timing:	Jan 19 2025 00:11:33
Module end 'content'
Timing:	Jan 19 2025 00:11:33
Script end

Main resources:

Total runtime	0.0163 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0048	587.9063	152.6250
Module start 'layout'	0.0048	0.0026	740.5313	39.4297
Module start 'content'	0.0074	0.0069	779.9609	89.0859
Module end 'content'	0.0143	0.0020	869.0469	30.3047
Script end	0.0163		899.3516

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	15.2208	14	0.0002
Check MTime	0.0011	6.7413	14	0.0001
Mysql Total
Database connection	0.0007	4.0894	1	0.0007
Mysqli_queries	0.0020	12.4989	3	0.0007
Looping result	0.0000	0.0803	1	0.0000
Template Total	0.0016	9.8	1	0.0016
Template load	0.0008	5.1782	1	0.0008
Template processing	0.0007	4.5433	1	0.0007
Override
Cache load	0.0006	3.7654	1	0.0006
General
dbfile	0.0020	12.5077	8	0.0003
String conversion	0.0000	0.0438	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs