Using UltimateParent to Resolve Top-Level Sections in Evolution CMS

When a template needs to know the main section of the current page, walking the tree by hand is repetitive and brittle. The old UltimateParent snippet was built for exactly this job: return the top-level ancestor, or the ancestor at a specific level, for the current resource or any resource ID you pass in.

Example

[[UltimateParent? &id=`12` &topLevel=`3`]]

In this example, the snippet resolves resource 12 and returns the ancestor at level 3. If you omit the &id parameter, the snippet works with the current resource.

Typical use cases

• highlighting the active top-level section in navigation
• switching layout fragments based on the current section
• loading shared TV data from a section root
• building breadcrumbs or helper links without hard-coding parent IDs

Why it is still useful

Even on newer Evo builds, the underlying problem has not changed: many templates need section context, not just the current document ID. A small helper like UltimateParent keeps that logic in one place and makes templates much easier to read.