Displaying Shopkeeper Product TVs Through catalogFill Data Sources

Catalog-driven commerce projects often need the storefront to read from one structure while Shopkeeper still handles the buying flow.

The donor behind this note showed a project where product data lived in catalog-oriented tables such as modx_catalog and modx_catalog_tmplvar_contentvalues, while the frontend still needed Shopkeeper-compatible output.

Example snippet call

[!catalogView? &dataType=`products` &parents=`87` &sortBy=`pagetitle` &sortDir=`asc`!]

What this pattern solves

keeping a structured catalog data source separate from ordinary resources
rendering storefront product data without duplicating everything by hand
connecting content modeling choices to a Shopkeeper-style sales flow

The general lesson is useful beyond this exact setup: once commerce data becomes richer than a plain page tree, it helps to separate the storage model from the display layer instead of pretending every product is just a normal content page with a few extra TVs.

Newer post

Filtering Ditto Results by Multi-Select TV Values

How to work with multi-select TV values in Ditto when one stored field needs to match more than one semantic category.

Older post

Filtering Resource Listings by a TV Value with DocLister or Ditto

How to filter a resource list by a TV value in Evolution CMS, with practical examples for both DocLister and Ditto.