Re: filteredChildNodes not working?

Thanks for your reply.

Strange as it seems - this works. I'm sure I've tried that before and  
in fact
it's logical, too, but imho this does not match the how-to's at zms- 
publishing.com.

I understand that a content object is a new object and so  
getParentNode is correct
- but I remember this working without specifying a reference and  
listing the
objects inside the current folder/context.

Mit freundlichen Grüßen
Sebastian Tänzer

tänzermedien e.K.
Agentur für Online-Medien:
Konzept / Design / Programmierung

c/o amcm GmbH
Kekuléstr. 39
53115 Bonn

Tel      0228-33646-23
Fax     0228-33646-13
Mobil  0174-333-7001

E-Mail [email protected]
WWW  http://www.taenzer.me

Am 07.05.2009 um 18:57 schrieb Jochen Schönfeldt:

>
>
> Maybe it works if you say
> getParentNode().filteredChildNodes(REQUEST,['remoteimage'])
>
> >Hello zms-list,
> >
> >I created a content object with the following template-code to  
> display
> >objects with the type "lightboximage":
> >
> ><dtml-in "filteredChildNodes(REQUEST,['remoteimage'])">
> ><dtml-var "getBodyContent(REQUEST)">
> ></dtml-in>
> >
> >and placed it inside a ZMS-Folder that contains several objects of
> >that type.
> >The list returned by filteredChildNodes is always empty.
> >
> >Double-checked with two different ZMS setups using ZMS 2.11.1-50
> >(Build #131k).
> >
> >What am I doing wrong?
> >
> >Mit freundlichen Grüßen
> >Sebastian Tänzer
>
> -- 
> Mit freundlichen Grüßen
> Jochen Schönfeldt
>
> ---------------------------------
> Elseware
> Weisestr. 31
> D-12049 Berlin
> Tel. ++49(0)30 62706012
> Mobil: ++49 (0)1762 2121806
> mailto:[email protected]
> http://www.elseware.de/
> ---------------------------------
>
>