Blog Sections Open
Using AjaxSearch with Multi-Select TV Filters
A guide to making AjaxSearch work with multi-select TV values when the stored data format is more complex than a simple string match.
AjaxSearch works best with straightforward fields, but many real Evolution CMS projects store important data in multi-select TVs. That is where filtering becomes more complicated: the value the editor sees is not always the value the query engine can match cleanly.
The real challenge
- Multi-select TVs often store combined or delimited values.
- AjaxSearch expects a clear condition it can evaluate.
- The filter UI still has to feel human-friendly.
The practical solution is to normalize the TV data contract before it reaches the search layer. In some projects that means matching against known stored values; in others it means reshaping the filter input before the query runs.
The core lesson is the same one we keep seeing across Evolution filters: do not confuse editor-friendly field presentation with query-friendly storage format.
Changing Wayfinder startId Based on the Current Section with if
How to switch Wayfinder startId dynamically with the if snippet so menu output follows the current section context.
Implementing AJAX Pagination for DocLister Listings
How to adapt AJAX pagination patterns from Ditto to DocLister listings in Evolution CMS.