Filtering multiTV Data Correctly with evoFilter and DocLister

Filtering multiTV-backed content sounds straightforward until you discover that the stored values do not behave like clean scalar fields. Comma-separated data, checkbox-like options, and price-oriented fields can all produce unexpected filter results when the filter engine expects a simpler value model.

The original issue around evoFilter, DocLister, and multiTV showed exactly that tension. The fix is usually not in the listing template, but in how the values are normalized before the filter layer sees them.

This is a recurring Evolution CMS problem in catalogs and spec-heavy pages, so it is worth treating as a reusable data-modeling lesson rather than a single addon quirk.