Blog Sections Open
Preparing Checkbox TV Data for autoFilter
Checkbox TVs become much easier to filter when their stored values are treated as data first and labels second.
The donor described a TV such as tvMaterial with checkbox-style values representing brands or material groups. This is exactly the kind of field that becomes difficult once filtering is added after the fact.
Why autoFilter struggles here
If the TV stores loosely formatted display text, filtering logic has to guess what each token means. That leads to brittle filters and confusing output.
Better approach
- store stable internal values
- render human-readable labels separately
- group related checkbox values intentionally instead of relying on visually similar text
Once the TV behaves like a proper data field instead of a presentation field, autoFilter becomes much easier to reason about and maintain.
Showing Parent Resource Titles in AjaxSearch Results
How to enrich AjaxSearch result templates with parent resource data so the result list shows more context than the matched page title alone.
Using Custom DocLister JSON Config Files Safely
How to work with custom DocLister JSON config files without mixing local overrides into core config paths or losing track of what the listing actually does.