This should steer you in the right direction:

<%!! Context:Indexes.GetIndexByPageId(Guid:<%inf_pageguid
%>).Parent.Page.Elements.GetElement(stf_placeholder).Value !!%>

The render tag above will enable you to obtain the value within a
placeholder of the parent page which you can then use to set the
required parameters on the page.


To look higher up in the tree, add extra 'Parent' tags:

<%!! Context:Indexes.GetIndexByPageId(Guid:<%inf_pageguid
%>).Parent.Parent.Page.Elements.GetElement(stf_placeholder).Value !!%>



Cheers,
Kim



On Oct 10, 7:59 am, Wayne Bouwmeester <[email protected]>
wrote:
> Are you using nav manager?
> If so, you could probably accomplish what you want with nav menus, or
> maybe with render tags.
> With render tags, you could look back to a field in the parent,
> grandparent, etc, and set a webtrends parameter.
> This might be easier than using keywords, plus you get the ability to
> fake inheritance for free if using nav manager.
> i.e. child pages don't actually need to be tagged to use a value from
> their parent for a metadata WT parameter.
> Wayne.
>
> On Oct 9, 12:35 pm, Ray <[email protected]> wrote:
>
> > Is there a means in RedDot where keywords could be assigned to
> > complete nodes in a site tree?
>
> > We're trying to use keywords as a means of applying some
> > categorization to our site to make it easier to obtain WebTrends
> > reports on various sections - and it's pretty tedious going through
> > pages and manually assigning keywords. We can't preassign them to the
> > content classes since the content classes are being used in different
> > nodes of the site tree.
>
> > Thanks,
> > Ray
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"RedDot CMS Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/reddot-cms-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to