Re: act: hiding {1}

Dan Durkin wrote: Is the use of the RequestParameterModule the new preferred way of doing this? In this case having a sitemap fragment like: But ofcourse :) I completely ignored what Ben actually tried to do and instead focussed on giving him the wrong answer :)

Re: act: hiding {1}

Leszek Gawron wrote: Jorg Heymans wrote: ../{1} IIRC {../1} Is the use of the RequestParameterModule the new preferred way of doing this? In this case having a sitemap fragment like: This eliminates the context switching {../1} WDYT? ---

act: hiding {1}

Hi, I'm trying to use the RequestParamAction, but when I do so, it blocks use of my normal {1} variable? Is there a way around this? Below is my sitemap excerpt. The first {1} works fine, but the second one does not. Is there a way to get at the {1} variable inside from within this ?

Re: act: hiding {1}

ignore this, i meant ofcourse {../1} as Irv already pointed out Jorg Heymans wrote: ../{1} IIRC Ben Anderson wrote: Hi, I'm trying to use the RequestParamAction, but when I do so, it blocks use of my normal {1} variable? Is there a way around this? Below is my sitemap excerpt. The first {1} wo

Re: act: hiding {1}

Jorg Heymans wrote: ../{1} IIRC {../1} -- Leszek Gawron [EMAIL PROTECTED] Project ManagerMobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812

Re: [Cocoon-Users] act: hiding {1}

Ben, you need to use {../1}. When you are inside an action, the "context" of the {} is the action itself. To get to the parent "context", you need to use .. Irv Ben Anderson wrote: Hi, I'm trying to use the RequestParamAction, but when I do so, it blocks use of my normal {1} variable? Is ther

Re: act: hiding {1}

../{1} IIRC Ben Anderson wrote: Hi, I'm trying to use the RequestParamAction, but when I do so, it blocks use of my normal {1} variable? Is there a way around this? Below is my sitemap excerpt. The first {1} works fine, but the second one does not. Is there a way to get at the {1} variable insi