Wednesday 29 July 2009 3:46:07 am - 3 replies

» Read full tutorial

Introduction

In an eZ Publish site structure, there are often nodes that hold information shown as a part of the full view of a different, master node. Showing the full view of the former nodes themselves or getting them as search results is usually unwanted. This is common in forums and articles with comments. If you have worked on a large eZ Publish project, you have probably used such nodes without referring to them by a specific name. This article explains what we call “helper nodes” and also explores the template and content model issues involved, relating specifically to search results.

Author Message

Rashod Ollison

Friday 18 June 2010 7:24:12 am

Thank you for this very useful information. master degree | nursing degree

Gaetano Giunta

Friday 27 August 2010 5:01:02 am

Please see issue 17148 for why terminating execution from within a node/view/full override template might not be the best idea in the world (at least when using ezdfs).

I'd recommend to always use the persistent_variable to pass the url to the pagelayout template even for http redirects, and let the pagelayout template execute the redirect operator...

Principal Consultant International Business
Member of the Community Project Board

Grenland Web (Jan Kudlicka)

Tuesday 31 August 2010 10:51:54 am

When this article was written using the redirect operator in node/view/full.tpl has been working perfectly.

However, as Gaetano Giunta mentions in the bug report, newer versions of eZ Publish use lock files when generating a cache file. Terminating the execution in the template code while generating a cache file causes that the lock file is not being removed and will block the next request to the same URL until the lock file has expired.

Jan Kudlicka | System Developer @ Grenland Web | http://www.grenlandweb.no

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

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

Main resources:

Total runtime0.0197 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.0076 589.5391152.6875
Module start 'layout' 0.00760.0035 742.226639.5234
Module start 'content' 0.01110.0054 781.750093.9297
Module end 'content' 0.01650.0031 875.679734.3047
Script end 0.0196  909.9844 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.003517.9371140.0003
Check MTime0.00157.6507140.0001
Mysql Total
Database connection0.00157.384310.0015
Mysqli_queries0.003015.042330.0010
Looping result0.00000.076310.0000
Template Total0.002110.510.0021
Template load0.00126.088810.0012
Template processing0.00094.413210.0009
Override
Cache load0.00083.818710.0008
General
dbfile0.00031.305280.0000
String conversion0.00000.059340.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