recursive override

Share » Forums » Setup & design » recursive override

Sunday 09 September 2007 8:21:28 pm - 2 replies

2 replies

Author	Message
Kåre Køhler Høvik	Monday 10 September 2007 12:45:08 am Hi Can you work around this by overriding the template using, depth, class, parent_class and section ( perhaps more ) conditions at the same time. See also: http://ez.no/doc/ez_publish/technical_manual/3_9/reference/template_override_conditions Kåre Høvik
paul bolger	Monday 10 September 2007 7:32:35 pm Hi Kåre So I could conceivably use parent_node + depth? Is depth in this context relative to the specified node, or is it absolute? Would the following: Match[parent_node]=2477 Match[depth]=2 give you two levels below node 2477, or two levels below the top level? As a matter of interest, how does navigation_part_identifier work? I would expect it to affect any node, or nodes, whose url includes a string, is this not the case? Thanks Paul Bolger

Author

Message

Monday 10 September 2007 12:45:08 am

Can you work around this by overriding the template using, depth, class, parent_class and section ( perhaps more ) conditions at the same time.

See also: http://ez.no/doc/ez_publish/technical_manual/3_9/reference/template_override_conditions

Kåre Høvik

paul bolger

Monday 10 September 2007 7:32:35 pm

Hi Kåre

So I could conceivably use parent_node + depth? Is depth in this context relative to the specified node, or is it absolute?

Would the following:

Match[parent_node]=2477
Match[depth]=2

give you two levels below node 2477, or two levels below the top level?

As a matter of interest, how does navigation_part_identifier work? I would expect it to affect any node, or nodes, whose url includes a string, is this not the case?

Thanks

Paul Bolger

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

design implementation by Netgen / design by Xvision

recursive override

Forums menu