ezpublish site design methods.

Next topic

Author	Message
Daniel Guerrier	Monday 28 March 2005 8:35:01 am There seems to be two options when creating a site using ezp. The first would be to rely solely on template overrides but that means you are locked into to basic look and feel of default skins if you don't feel like creating a new one. The second is to create a bunch of templates that extract data and include them where needed. Is there a happy medium or is this totally of base?
Jonathan Dillon-Hayes	Monday 28 March 2005 12:07:44 pm Heya: I'm not really sure how those are different. At it's core, whenever you're working with a OO framework, you have to have a method to express your data that's generated by your classes into something your users can use. Whether you're building eZ Publish or your own handbuilt CMS, you're always going to have to do this. The second method your describing is more proceedural progamming (essentially using ez as a basic database). It's not really taking advantage of the power of eZ Publish, not it's OO underpinnings. If you just want to get a default style and customize it, get one of the pre-designed results of the recent template contest: http://ez.no/community/contribs/site_styles Otherwise, yes, you do have to set up templates to express the data. Actually, eZ Publish is really intelligently build with the "overrrides", because it provides profound flexibility. You got to remember, this system is design to build a system that scales well, and is less work in the big picture. Some modicum of effort is required to set it up initially. Jonathan --------- FireBright provides advanced eZ deployment with root access http://www.FireBright.com/
Frey Staso	Tuesday 29 March 2005 8:26:38 am Actually its not really that hard once you play with it. You can customize the overrides to fit your own needs quite easily. Each .tpl override is more or less just html code, just make sure you have a loop to display the object you are viewing (like a folder) and or the objects underneath where you are viewing (like an article) If you follow along with the chess tutorial you'll see its pretty easy as long as you remember that each override goes inside of the pagelayout.tpl. while these DO override the "standard" look and feel of ezpublish, the name is a little misleading. Really you are making a small tpl (basically html) file to display your data, don't really think about it "overriding" anything. Open some of the overrides inside of dreamweaver or your favorite editor and try making small changes. Youll quickly see how this CMS can be used.

Author

Message

Monday 28 March 2005 8:35:01 am

There seems to be two options when creating a site using ezp.

The first would be to rely solely on template overrides but that means you are locked into to basic look and feel of default skins if you don't feel like creating a new one.

The second is to create a bunch of templates that extract data and include them where needed.

Is there a happy medium or is this totally of base?

Jonathan Dillon-Hayes

Monday 28 March 2005 12:07:44 pm

Heya:

I'm not really sure how those are different.

At it's core, whenever you're working with a OO framework, you have to have a method to express your data that's generated by your classes into something your users can use.

Whether you're building eZ Publish or your own handbuilt CMS, you're always going to have to do this.

The second method your describing is more proceedural progamming (essentially using ez as a basic database). It's not really taking advantage of the power of eZ Publish, not it's OO underpinnings.

If you just want to get a default style and customize it, get one of the pre-designed results of the recent template contest:
http://ez.no/community/contribs/site_styles

Otherwise, yes, you do have to set up templates to express the data. Actually, eZ Publish is really intelligently build with the "overrrides", because it provides profound flexibility.

You got to remember, this system is design to build a system that scales well, and is less work in the big picture. Some modicum of effort is required to set it up initially.

Jonathan

---------
FireBright provides advanced eZ deployment with root access
http://www.FireBright.com/

Frey Staso

Tuesday 29 March 2005 8:26:38 am

Actually its not really that hard once you play with it. You can customize the overrides to fit your own needs quite easily. Each .tpl override is more or less just html code, just make sure you have a loop to display the object you are viewing (like a folder) and or the objects underneath where you are viewing (like an article)

If you follow along with the chess tutorial you'll see its pretty easy as long as you remember that each override goes inside of the pagelayout.tpl.

while these DO override the "standard" look and feel of ezpublish, the name is a little misleading. Really you are making a small tpl (basically html) file to display your data, don't really think about it "overriding" anything.

Open some of the overrides inside of dreamweaver or your favorite editor and try making small changes. Youll quickly see how this CMS can be used.

eZ debug

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

Main resources:

Total runtime	0.7724 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.0083	589.0313	152.6250
Module start 'layout'	0.0083	0.0028	741.6563	39.4453
Module start 'content'	0.0112	0.7597	781.1016	564.8906
Module end 'content'	0.7709	0.0015	1,345.9922	12.1641
Script end	0.7724		1,358.1563

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.4543	16	0.0002
Check MTime	0.0015	0.1896	16	0.0001
Mysql Total
Database connection	0.0014	0.1858	1	0.0014
Mysqli_queries	0.7155	92.6304	59	0.0121
Looping result	0.0006	0.0778	57	0.0000
Template Total	0.7072	91.6	2	0.3536
Template load	0.0027	0.3434	2	0.0013
Template processing	0.7046	91.2154	2	0.3523
Template load and register function	0.0001	0.0146	1	0.0001
states
state_id_array	0.0069	0.8899	1	0.0069
state_identifier_array	0.0033	0.4264	2	0.0016
Override
Cache load	0.0022	0.2883	24	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.0593	3	0.0002
Fetch class attribute name	0.0010	0.1269	4	0.0002
XML
Image XML parsing	0.0007	0.0947	3	0.0002
class_abstraction
Instantiating content class attribute	0.0000	0.0012	4	0.0000
General
dbfile	0.0022	0.2881	16	0.0001
String conversion	0.0000	0.0012	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
4	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	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 11 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs