Blog Sections Open
Choosing Between Absolute and Relative Paths in Evolution CMS Templates
A practical link and asset-path note for Evolution CMS themes that mix base href, generated links, and snippet output.
Path bugs in Evolution CMS are rarely caused by one component alone. They usually happen when a project mixes several URL styles at once: a base href, root-relative assets, generated snippet links, and template fragments written with different assumptions.
Common friction points
<base href>changes how relative links resolve.- Static asset includes may use plain relative paths.
- Snippets such as Wayfinder, DocLister, and AjaxSearch may generate root-relative links.
Practical rule
Pick a consistent site-wide path strategy. If the project uses a base href deliberately, make sure templates and generated outputs are compatible with it. If it does not, prefer root-relative or fully generated URLs and avoid ambiguous relative asset references.
Consistency matters more than ideology here. A mixed strategy is what causes most path bugs.
Fixing tagManager2 AJAX Filters When Products Disappear
How to troubleshoot tagManager2 AJAX filtering when the filter UI updates but the product list vanishes or stops responding correctly.
Why AjaxSearch Highlighting Can Break Result Excerpts
How to troubleshoot AjaxSearch result excerpts when highlighting logic wraps matches incorrectly and damages the visible snippet output.