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 » Discussions » Helper Child Nodes: User-Friendly...
expandshrink

Wednesday 29 July 2009 12:46:07 pm - 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.

Friday 18 June 2010 4:24:12 pm

The reply has been removed because of violation of forum rules.

Friday 27 August 2010 2:01:02 pm

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...

Modified on Tuesday 31 August 2010 7:27:35 pm by Gaetano Giunta

Tuesday 31 August 2010 7:51:54 pm

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.

expandshrink

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

36 542 Users on board!

Forums menu

Proudly Developed with from