Resolving External Catalog Aliases Before Evolution CMS Routing Runs

When product data lives outside the resource tree, alias resolution must happen before the normal document lookup finishes.

This donor topic described a common integration pattern: the catalog data sits in another database, but the pages must still render inside the Evolution CMS project.

The Routing Problem

If no real Evolution CMS document exists for the requested alias, the normal document resolver will fail before your custom product logic gets a chance to run.

What the Project Needs

An early routing hook that checks whether the alias belongs to an external product record.
A controller or rendering layer that can build the page from external data.
A clear canonical URL strategy so external product pages still behave like first-class site pages.

The key architectural lesson is that hybrid content should be routed intentionally. It should not depend on a late template hack after normal document resolution has already failed.

Newer post

Sending eForm Submissions to Multiple Recipients

How to deliver one eForm submission to several recipients when a comma-separated address list is not enough in your setup.

Older post

Building Multi-Level Menus with Wayfinder

How to approach a complex nested navigation layout in Evolution CMS using Wayfinder instead of hard-coded static HTML.