Blog Sections Open

Fixing tagManager2 AJAX Filters When Products Disappear

A practical debugging note for Evolution CMS catalog filters built with tagManager2 and AJAX output.

tagManager2 can feel fine until the AJAX layer is introduced. Then a site may render the filter controls correctly, but the product list disappears, pagination breaks, or the reset action behaves unpredictably.

Typical structure

[[tmFilters? &jsMap=`1` &toPlaceholder=`filters`]]
<div id="filters">...[[+filters]]...</div>
<div class="product_list">[[!tmCatalog]]</div>
<ul class="pages">[[!+page.nav]]</ul>

Where the breakdown usually happens

  • The AJAX response does not re-render all dependent blocks.
  • The filter form and the product list disagree about the current state.
  • Pagination placeholders are not refreshed together with results.

For Evo filtering flows, the safest design is to treat filters, results, and pagination as one response contract. If one of those regions is updated alone, the interface quickly drifts out of sync.

Newer post

Showing Introductory Text Only on the First Page of Pagination

How to keep explanatory page text visible only on the first page of a paginated listing instead of repeating it across every paginated view.

Older post

Choosing Between Absolute and Relative Paths in Evolution CMS Templates

How to keep asset URLs, snippet outputs, and generated links consistent by understanding when absolute paths and relative paths should each be used.