What's the difference between the 'standard' and the 'base' directory?

Next topic

Author	Message
Igor Paffen	Monday 30 August 2004 10:37:38 am I use "The Scandinavian Check Mates" website for learning the system. When no specific template is made in the 'TSCM' directory, sometimes the 'standard' directory is used and sometimes the 'base' directory. What's the difference between the 'base' directory and the 'standard' directory?
Lazaro Ferreira	Monday 30 August 2004 10:58:05 am Hi, AFAIK, the base directory is used to support ezp custom setup, i.e : At the time of setup you can ask ezp to install some modules, like foruns, polls, feedback form, and the likes, behind the scene ezp setup add a lot of customization code in form of templates, override settings, etc, as result you get a lot of ready to use ezp funcionality On the other hand, the standard ezp directory is the place where every ezp functionality found a default, a last resource where ezp can fall back, in case no override or customization exist This is at the heart of ezp filosophy, every module, object or component supported by the system has a default way to present or appear, that's the standard way in the standard directory I'm not sure but if you ask EZP to do a plain installation, (no custom module), you will probably get only the standard directory Lazaro Ferreira http://www.mzbusiness.com Lazaro http://www.mzbusiness.com

Author

Message

Monday 30 August 2004 10:37:38 am

I use "The Scandinavian Check Mates" website for learning the system. When no specific template is made in the 'TSCM' directory, sometimes the 'standard' directory is used and sometimes the 'base' directory. What's the difference between the 'base' directory and the 'standard' directory?

Lazaro Ferreira

Monday 30 August 2004 10:58:05 am

Hi,

AFAIK, the base directory is used to support ezp custom setup, i.e : At the time of setup you can ask ezp to install some modules, like foruns, polls, feedback form, and the likes, behind the scene ezp setup add a lot of customization code in form of templates, override settings, etc, as result you get a lot of ready to use ezp funcionality

On the other hand, the standard ezp directory is the place where every ezp functionality found a default, a last resource where ezp can fall back, in case no override or customization exist

This is at the heart of ezp filosophy, every module, object or component supported by the system has a default way to present or appear, that's the standard way in the standard directory

I'm not sure but if you ask EZP to do a plain installation, (no custom module), you will probably get only the standard directory

Lazaro Ferreira
http://www.mzbusiness.com

Lazaro
http://www.mzbusiness.com

eZ debug

Timing:	Jan 31 2025 04:27:05
Script start
Timing:	Jan 31 2025 04:27:05
Module start 'layout'
Timing:	Jan 31 2025 04:27:05
Module start 'content'
Timing:	Jan 31 2025 04:27:06
Module end 'content'
Timing:	Jan 31 2025 04:27:06
Script end

Main resources:

Total runtime	1.1057 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.0051	588.6172	151.2734
Module start 'layout'	0.0051	0.0024	739.8906	36.7266
Module start 'content'	0.0075	1.0973	776.6172	882.3594
Module end 'content'	1.1047	0.0009	1,658.9766	7.7656
Script end	1.1056		1,666.7422

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.2734	16	0.0002
Check MTime	0.0012	0.1101	16	0.0001
Mysql Total
Database connection	0.0007	0.0593	1	0.0007
Mysqli_queries	1.0587	95.7517	54	0.0196
Looping result	0.0005	0.0440	52	0.0000
Template Total	1.0649	96.3	2	0.5325
Template load	0.0022	0.1978	2	0.0011
Template processing	1.0627	96.1187	2	0.5314
Template load and register function	0.0015	0.1322	1	0.0015
states
state_id_array	0.0010	0.0933	1	0.0010
state_identifier_array	0.0009	0.0841	2	0.0005
Override
Cache load	0.0018	0.1588	12	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0007	0.0588	2	0.0003
Fetch class attribute name	0.0018	0.1671	2	0.0009
XML
Image XML parsing	0.0002	0.0206	2	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0006	2	0.0000
General
dbfile	0.0043	0.3926	10	0.0004
String conversion	0.0000	0.0007	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
3	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: 8 Number of unique templates used: 5

Time used to render debug report: 0.0001 secs