Using Custom DocLister JSON Config Files Safely

DocLister config files make complex listings easier to reuse, but only if the project keeps the file structure disciplined.

The donor behind this post used a custom JSON config file such as /snippets/DocLister/config/custom/afilter.json to keep a listing definition outside the page template.

Example

{
  "filters": "OR(tv:grafik:is: ;tv:grafik:is: )",
  "display": "20",
  "tpl": "fvyd",
  "parents": "30"
}

Why this approach is good

complex listings become reusable
template code stays shorter and more readable
the listing logic gets one explicit place to live

The original advice also warned against confusing custom config locations with core config files. That warning still matters. Put project-specific listing behavior in project-specific config files, not in shared core definitions you will later forget you modified.

Newer post

Preparing Checkbox TV Data for autoFilter

How to structure checkbox TV values so autoFilter can work with them predictably instead of receiving loosely formatted label strings.

Older post

Filtering Ditto Output with Checkbox TV Values

How checkbox TVs interact with Ditto filters and what to watch for when the stored values do not behave like a simple one-value field.