Is there a reason why this doesn't work the other way around, for example:
I have an area of the website which I have restricted access to, I wanted to have a parent page that takes care of the restrictions for all child pages.
What I did was have a parent with a restricted_behavior and a body part that shows either a 'registered' or a 'not_registered' page parts depending if the user is registered or not.
Then I have child pages hat do not have a body page part, so radiant finds the body page part in the parent, but if the tags I used in the parent are not in the child behavior I get errors that the tags are not recognized, which made me duplicate the tags to all behaviors I use with the page children.
Is this the way it suppose to work? Is there any other way of doing what I want to do?
Dror

On 9/6/06, John W. Long < [EMAIL PROTECTED]> wrote:
Bodhi wrote:
> On Sep 6, 2006, at 7:12 AM, Justin Marney wrote:
>
>> The ability to have multiple child pages each with thier own
>> behavior, and subsequently display them all on the parent page is a
>> general technique that gets used quite a bit in Radiant
>
> This gives me the idea of creating something on the wiki about
> "Radiant Recipes" or something, documenting common usage patterns,
> tips, and radiant idioms. What do people think?

Perhaps the How To section would work for this?

   http://dev.radiantcms.org/radiant/wiki/HowTos

--
John Long
http://wiseheartdesign.com
_______________________________________________
Radiant mailing list
[email protected]
http://lists.radiantcms.org/mailman/listinfo/radiant

_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to