Site built with functionality from several packages

Author Message

Neil Kanth

Monday 02 October 2006 6:03:28 pm

I would like implement the functionality of the, forum, gallery, weblog and corp packages into one (1) site.

Since I cannot import more than one (1) package per site; is it best to import the <i>contentobjects</i> or create the <i>contectobjects</i>??

Also, when a <i>contentobject</i> is imported, should I have new folders (...files etc) created when similar folders (...files etc) already exist?

Lastly, I will have several <i>sections</i>, one (1) for each main-menu item and I would like to have a different template for each, is it best to create additional <i>content classes</i> even though they would be similar?

Thanks.

Claudia Kosny

Friday 06 October 2006 3:00:16 am

Hi Neil

I don't see a reason to create the contentobjects if you can import them. The few contenobjects I imported from the EZ website provided enough information during imprt to see what changes are made.

In regards to the folders - I would say this is up to you. I don't like to have many folders so Iwould try to use the same folders for contentobjects that belong to the same topic.

In regards to the sections I just would use override conditions to select the template.
http://ez.no/doc/ez_publish/technical_manual/3_8/reference/template_override_conditions/node_view_tpl
Having additional content classes for similar content kind of defeats the idea of an template system to separate the content from the display.

Greetings from Luxembourg

Claudia

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

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

Main resources:

Total runtime0.0142 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0044 588.3828151.2422
Module start 'layout' 0.00440.0026 739.625036.7109
Module start 'content' 0.00700.0060 776.335990.1094
Module end 'content' 0.01290.0012 866.445329.9922
Script end 0.0142  896.4375 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002114.7560140.0001
Check MTime0.00107.0841140.0001
Mysql Total
Database connection0.00074.769710.0007
Mysqli_queries0.002417.161030.0008
Looping result0.00000.154510.0000
Template Total0.00096.410.0009
Template load0.00085.283710.0008
Template processing0.00021.133710.0002
Override
Cache load0.00053.217910.0005
General
dbfile0.002618.321580.0003
String conversion0.00000.040340.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs