This site has been archived and you can no longer log in or post new messages. For up-to-date community resources please visit ezplatform.com

eZ Community » Forums » General » Problems adding new template
expandshrink

Problems adding new template

Problems adding new template

Friday 11 June 2010 9:57:29 am - 8 replies

I just added a new template and the first one works - I just couldn't put it where I would like. This is the process I used:

1. I created a class called page_article
2. I created a file called  page_article.tpl and placed this in override/templates/
3. I created a INI file called override.ini.append.php 

In this ini file, I had the following code:

[page_article]
Source=node/view/full.tpl
MatchFile=page_article.tpl
Subdir=templates

Following the same process, and adding new code in INI file, my INI file now looks like this:

[page_article]
Source=node/view/full.tpl
MatchFile=page_article.tpl
Subdir=templates
[complaint]
Source=node/view/full.tpl
MatchFile=complaint.tpl
Subdir=templates

My problem now, is that nothing works backend in admin mode (more or less).
The debug output gives me the following error:

Error: eZTemplateDesignResource :: overrideArray

 Custom match file: path 'complaint.tpl' not found in any resource. Check the template settings in settings/override.ini

I'm guessing it's because now I have two statements telling the systems to override full.tpl.
But guess what - I don't want to overrride any templates. I have created my own custom templates - and I want to use them.

Why is there no documentation explaining how to add new custom tempaltes step by step?
And no, thre is nothing telling my how to accomplish this in http://ez.no/doc/ez_publish/technical_manual/4_x/templates 

 

Any help appreciated.

Modified on Friday 11 June 2010 10:09:40 am by Steven Stieng

Friday 11 June 2010 10:23:05 am

1. You are missing conditions in your override setting, menaing the last one will "overrride" the first one in every case.

http://ez.no/doc/ez_publish/technical_manual/4_x/reference/template_override_conditions

2. As for the admin error, I guess you added the template in a design only used by front end (for instance ezwebin) but not back end, and then added the override ini setting globally in settings/override or extension/<extension>/settings/, when it should have been placed in settings/siteaccess/<frontend_siteaccess>/ if you inteded to only use it in frontend and not backend(admin).

3. There is a tutorial for creating ezp sites, its a bit old but still relevant (concepts are the same):

http://ez.no/ezpublish/documentation/building_an_ez_publish_site (see links to the right to start tutorial)

Hope this helps,
André

Modified on Friday 11 June 2010 10:23:26 am by André R

Friday 11 June 2010 10:49:58 am

Thanks for the reply André.

1. That's what I thought.
2. If I remove the last adition to the INI file, admin interface works fine.
3. Yeah, I've looked at this. And it only tells my what I've already done.

To ask in another way:

4. Do I always have to use override when creating new templates?
5. Where do I place new templates?
6. Where is the connection between a new template.tpl file and equivalent class name?

I'm still trying to get my head around ez Publish. But it's extremely difficult. There are so many places where one can put a file - and too many INI files to get an overview.

 And the lack of tutorials / examples. http://ez.no/doc does not prived tutorials or any good examples.

Modified on Friday 11 June 2010 10:56:24 am by Steven Stieng

Friday 11 June 2010 11:52:39 am

UPDATE

 This is my new override.ini.append.php file:

[page_article]
Source=node/view/full.tpl
MatchFile=page_article.tpl
Subdir=templates
Match['class_identifier']=page_article

[complaint]
Source=node/view/full.tpl
MatchFile=complaint.tpl
Subdir=templates
Match['class_identifier']=complaint

My file is located in: C:\wamp\www\mysite\settings\override

My templates files are located in:
C:\wamp\www\mysite\extension\ezwebin\design\ezwebin\override\templates 

I'm still getting these errors:

Error: eZTemplateDesignResource:omg.gif EmoticonverrideArray

Jun 11 2010 11:49:34

 

Custom match file: path 'page_article.tpl' not found in any resource. Check the template settings in settings/override.ini

Error: eZTemplateDesignResource:omg.gif EmoticonverrideArray, tried files

Jun 11 2010 11:49:34

 

design/admin2/override/templates/page_article.tpl, extension/ezmultiupload/design/admin/override/templates/page_article.tpl, extension/ezjscore/design/admin/override/templates/page_article.tpl, design/admin/override/templates/page_article.tpl, extension/ezmultiupload/design/standard/override/templates/page_article.tpl, extension/ezjscore/design/standard/override/templates/page_article.tpl, extension/ezwt/design/standard/override/templates/page_article.tpl, extension/ezstarrating/design/standard/override/templates/page_article.tpl, extension/ezgmaplocation/design/standard/override/templates/page_article.tpl, extension/ezoe/design/standard/override/templates/page_article.tpl, extension/ezodf/design/standard/override/templates/page_article.tpl, design/standard/override/templates/page_article.tpl

Error: eZTemplateDesignResource:omg.gif EmoticonverrideArray

Jun 11 2010 11:49:34

 

Custom match file: path 'complaint.tpl' not found in any resource. Check the template settings in settings/override.ini

Error: eZTemplateDesignResource:omg.gif EmoticonverrideArray, tried files

Jun 11 2010 11:49:34

 

design/admin2/override/templates/complaint.tpl, extension/ezmultiupload/design/admin/override/templates/complaint.tpl, extension/ezjscore/design/admin/override/templates/complaint.tpl, design/admin/override/templates/complaint.tpl, extension/ezmultiupload/design/standard/override/templates/complaint.tpl, extension/ezjscore/design/standard/override/templates/complaint.tpl, extension/ezwt/design/standard/override/templates/complaint.tpl, extension/ezstarrating/design/standard/override/templates/complaint.tpl, extension/ezgmaplocation/design/standard/override/templates/complaint.tpl, extension/ezoe/design/standard/override/templates/complaint.tpl, extension/ezodf/design/standard/override/templates/complaint.tpl, design/standard/override/templates/complaint.tpl

 

It does not help putting the files in /full directory, and changing INI file to MatchFile=full/page_article.tpl.

Modified on Friday 11 June 2010 11:53:03 am by Steven Stieng

Friday 11 June 2010 12:54:33 pm

Someone else having the same problem as well:

http://share.ez.no/forums/general...te-settings-in-settings-override.ini

Friday 11 June 2010 2:02:03 pm

> 4. Do I always have to use override when creating new templates?

Only when overriding a template using a set of conditions(aka conditional overrides), if you want to create a reusable template stub for use with include in templates, then you can just place it in template folder.

Or if you create your own eZ Publish module, you normally just place the needed files in template folder as well, optimally using a naming convention like this: template/<module>/<view>.tpl.

Example: content module as used for all content in eZ Publish (articles / folders / forums... all content classes), it's system url uses the following form: content/view/<view>/<node_id> where <view> can be anything, but normally 'full' or 'line', if 'full' then the following template is used content/view/full.tpl if you want to have a specific template for this node (or the frontpage class that you would normallt have on this node) then you need to override that template with a conditional template.

> 5. Where do I place new templates?

As said above, direct includes in: templates/ and for override.ini overrides: override/templates/

> 6. Where is the connection between a new template.tpl file and equivalent class name?

the connection between a content class's custom templates and it's templates are always defined in override.ini.

> It does not help putting the files in /full directory, and changing INI file to MatchFile=full/page_article.tpl.

Where do you get this errors? everywhere? admin? or only in specific places in admin like for instance: class/view/<id> with 'override templates' button disabled?
Hint: If only last option, then you can safely ignore it, it's a bug in how the system loads other siteaccesses then it self and tries do look up all overrides without having access to all design folders of those siteaccesses.

Thursday 13 January 2011 10:45:30 am

> 4. Do I always have to use override when creating new templates?

Only when overriding a template using a set of conditions(aka conditional overrides), if you want to create a reusable template stub for use with include in templates, then you can just place it in template folder.

This is something I never really understood, because everything I found documented was intertwined with several conditions, so maybe I can finally get an answer this time:

Does this mean that I only need to create a new content class like "report", and then create a template with the same name (report.tpl) to have the template used by the system? If so, where would I place such a template? I did a search on "article.tpl" in the installation tree and ended up with 16 hits, all of them with an "override" folder in the path...

Thursday 13 January 2011 2:32:59 pm

Does this mean that I only need to create a new content class like "report", and then create a template with the same name (report.tpl) to have the template used by the system?

No.

If you want to ALWAYS use your own template instead of the given template, you do not need any override condition; eg: always use your own tpl for login page (user/login.tpl), or always use your own template for displaying ezstarrating attributes (content/datatype/view/ezstarrating.tpl)

By default all content is shown using the same template: node/view/full.tpl

So if you want to use a different template for 'only some content', such as a specific content class, you do need an override rule and a template in the override folder

Thursday 13 January 2011 3:54:33 pm

OK, then I bury that hope. But I would really really like to ask two more questions:

1) I saw different instructions regarding the override.append.ini.php, one said to put it into the design folder, one spoke of the siteaccess folder. Which one is right?

2) Overriding is mentioned pretty often with custom templates, and through debug I can find out which article.tpl is called at what time, but supposed I want to create above mentioned report.tpl, do I put the file into the same folder as a corresponding article.tpl (all of them in some override path already) or do I need to override these overrides - and if, where?

Edit: OK, I finally got it...

Modified on Tuesday 18 January 2011 10:40:55 am by Olaf Fichtner

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from