Better directory names

Next topic

Author	Message
James Ward	Sunday 01 February 2004 11:58:29 am I believe the directories created during installation could be more intuitive. Currently if I install a plain design with a user site called "foo" and an admin site called "foo_admin" I get a "foo" and "foo_admin" directory in the siteaccess directory. However the design files are stored in a directory called "plain", in my opinion it would make more sense for this design directory to be called "foo". Also any files uploaded to be used for "foo" will be stored in the var directory named "plain", again I feel it would make more sense to call this directory "foo". So we would end up with the following after install: /design/foo /siteaccess/foo /siteaccess/foo_admin /var/foo Anyone else think this makes more sense? I used to change the directory names manually but with more files being installed to the var directory during the setup this is starting to create problems. working at www.wardnet.com blogging at www.jamesward.ca
Harry Oosterveen	Sunday 01 February 2004 12:42:38 pm That would make sense if there is a one-to-one relation between sites and designs. This is not necessarily the case. I am working on a server where we host and maintain multiple sites. All admin sites use the same standard 'admin' design, only the front end of each site has a different design. Some sites come in several languages; from an eZ publish point of view, they are different sites (different siteaccess folders), but they share the same design.
James Ward	Sunday 01 February 2004 10:39:15 pm Good Point. What about the var directory then? Odds are each site access will have its own set of uploaded and cached files. Should the var directory not be renamed to reflect the site access name then? working at www.wardnet.com blogging at www.jamesward.ca

Author

Message

Sunday 01 February 2004 11:58:29 am

I believe the directories created during installation could be more intuitive. Currently if I install a plain design with a user site called "foo" and an admin site called "foo_admin" I get a "foo" and "foo_admin" directory in the siteaccess directory. However the design files are stored in a directory called "plain", in my opinion it would make more sense for this design directory to be called "foo". Also any files uploaded to be used for "foo" will be stored in the var directory named "plain", again I feel it would make more sense to call this directory "foo". So we would end up with the following after install:
/design/foo
/siteaccess/foo
/siteaccess/foo_admin
/var/foo

Anyone else think this makes more sense? I used to change the directory names manually but with more files being installed to the var directory during the setup this is starting to create problems.

working at www.wardnet.com
blogging at www.jamesward.ca

Harry Oosterveen

Sunday 01 February 2004 12:42:38 pm

That would make sense if there is a one-to-one relation between sites and designs. This is not necessarily the case.

I am working on a server where we host and maintain multiple sites. All admin sites use the same standard 'admin' design, only the front end of each site has a different design. Some sites come in several languages; from an eZ publish point of view, they are different sites (different siteaccess folders), but they share the same design.

James Ward

Sunday 01 February 2004 10:39:15 pm

Good Point.
What about the var directory then? Odds are each site access will have its own set of uploaded and cached files. Should the var directory not be renamed to reflect the site access name then?

working at www.wardnet.com
blogging at www.jamesward.ca

eZ debug

Timing:	Jan 18 2025 15:05:46
Script start
Timing:	Jan 18 2025 15:05:46
Module start 'layout'
Timing:	Jan 18 2025 15:05:46
Module start 'content'
Timing:	Jan 18 2025 15:05:46
Module end 'content'
Timing:	Jan 18 2025 15:05:46
Script end

Main resources:

Total runtime	0.6130 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0061	587.9141	152.6250
Module start 'layout'	0.0061	0.0027	740.5391	39.4453
Module start 'content'	0.0087	0.6027	779.9844	537.5313
Module end 'content'	0.6114	0.0016	1,317.5156	12.1719
Script end	0.6130		1,329.6875

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.5363	16	0.0002
Check MTime	0.0014	0.2292	16	0.0001
Mysql Total
Database connection	0.0014	0.2302	1	0.0014
Mysqli_queries	0.5557	90.6525	57	0.0097
Looping result	0.0006	0.0964	55	0.0000
Template Total	0.5803	94.7	2	0.2902
Template load	0.0032	0.5276	2	0.0016
Template processing	0.5771	94.1342	2	0.2885
Template load and register function	0.0001	0.0183	1	0.0001
states
state_id_array	0.0009	0.1521	1	0.0009
state_identifier_array	0.0009	0.1397	2	0.0004
Override
Cache load	0.0025	0.4141	18	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.1003	2	0.0003
Fetch class attribute name	0.0012	0.1971	5	0.0002
XML
Image XML parsing	0.0032	0.5251	2	0.0016
class_abstraction
Instantiating content class attribute	0.0000	0.0022	6	0.0000
General
dbfile	0.0027	0.4412	21	0.0001
String conversion	0.0000	0.0015	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
2	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
3	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 13 Number of unique templates used: 6

Time used to render debug report: 0.0002 secs