How to make New design extension

Author Message

paul bolger

Monday 01 September 2008 4:56:45 pm

Can anybody point me to a succinct guide to making a new design extension? A plain install with the website interface seems to have settings and design files in both the /design and /settings folders as well as the extension, although the design folders are empty. Are these all necessary?

Paul Bolger

André R.

Tuesday 02 September 2008 10:12:09 am

The design folder is created by the installer and can safely be removed (might be the one used if you create a template override with the admin interface though).

As for creating extension there is a article on it:
http://ez.no/developer/articles/an_introduction_to_developing_ez_publish_extensions

But might not be what you where looking for?

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Andrew Duck

Wednesday 17 September 2008 10:13:57 am

Hi Paul,

I am unaware of a short guide to design extensions at the moment, though it certainly is something I will consider writing in the near future if others are looking for similar information.

In short you are looking to replicate the identical directory structure from a normal design in the /design folder.

Your new extension, for instance "myext" with a design "mydesign".

/extension/myext/design/mydesign

Within this design you would have folders for images, javascript, override/templates, stylesheets and templates as per the ezwebin and similar extensions.

The one other thing that is required is a settings folder: /extension/myext/settings/ with a design.ini.append.php file specifying:

<?php /* #?ini charset="utf-8"?

[ExtensionSettings]
DesignExtensions[]=myext

*/ ?>

Once you have activated your extension via the administration interface (Setup -> Extension) or via settings/override/site.ini.append.php, eZ Publish will check within your activated extensions and register the fact that <i>myext</i> contains a design.

You can then specify that design name, <i>mydesign</i> within your siteaccess [DesignSettings] block.

I hope that provides a quick overview as to how you can get up and running with your design inside an extension. If you run into any problems shoot back more questions :)

Regards,
Andrew.

Andrew Duck, Executive Director, Quiqcorp Limited
eZ Certified Developer and Trainer.
Member of the Community Project Board
http://quiqcorp.com | http://twitter.com/andrewduck

DeAndre Johnson

Monday 03 November 2008 8:12:59 pm

Yes I also would like for a guide to making a new design extension. That would be a great thing to have.

I am, because I choose to be!

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 18 2025 19:10:06
Script start
Timing: Jan 18 2025 19:10:06
Module start 'layout'
Timing: Jan 18 2025 19:10:06
Module start 'content'
Timing: Jan 18 2025 19:10:06
Module end 'content'
Timing: Jan 18 2025 19:10:06
Script end

Main resources:

Total runtime0.8679 sec
Peak memory usage4,096.0000 KB
Database Queries64

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0073 589.1563152.6406
Module start 'layout' 0.00730.0031 741.796939.4766
Module start 'content' 0.01040.8560 781.2734644.7734
Module end 'content' 0.86640.0015 1,426.046916.1406
Script end 0.8679  1,442.1875 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00320.3709160.0002
Check MTime0.00130.1525160.0001
Mysql Total
Database connection0.00180.204210.0018
Mysqli_queries0.803092.5213640.0125
Looping result0.00090.1014620.0000
Template Total0.826595.220.4132
Template load0.00210.240220.0010
Template processing0.824494.987020.4122
Template load and register function0.00010.011410.0001
states
state_id_array0.00090.101710.0009
state_identifier_array0.00070.078820.0003
Override
Cache load0.00160.1845290.0001
Sytem overhead
Fetch class attribute can translate value0.00090.098840.0002
Fetch class attribute name0.00180.212280.0002
XML
Image XML parsing0.00230.269540.0006
class_abstraction
Instantiating content class attribute0.00000.001280.0000
General
dbfile0.00150.1697370.0000
String conversion0.00000.000940.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
4content/datatype/view/ezimage.tpl<No override>extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tplEdit templateOverride template
4content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
7content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
2content/datatype/view/ezxmltags/line.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/line.tplEdit templateOverride template
1content/datatype/view/ezxmltags/literal.tpl<No override>extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 20
 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs