Blog Sections Open
Getting the Current Page Alias Through the Evolution CMS API
When a snippet needs the current alias, pull it from the loaded document context instead of rebuilding URL logic manually.
Fetching the current page alias is a small task, but it often appears inside route-aware snippets, custom breadcrumbs, exports, and integrations. The safe approach is to read it from the current document context rather than derive it from the URL string.
Once a snippet works against the current resource object or document data, alias-dependent logic becomes much easier to test and far less brittle when URL rules change later.
Filtering Ditto Output by Tag TVs Without Relying on Generated Query Strings
How to structure Ditto tag filtering when products need to appear on predefined pages instead of generated tag-result URLs.
Requiring a Consent Checkbox in eForm Without Losing Filled Fields
How to block form submission until a consent checkbox is checked while still preserving the user’s entered values.