Blog Sections Open
Making shk_widget Render the Right Product Parameter
Shopkeeper parameter TVs can look correct in the manager but still output the wrong thing in templates. The original question here came from shk_widget rendering a value based on the wrong identifier when a TV held sever
Shopkeeper parameter TVs can look correct in the manager but still output the wrong thing in templates. The original question here came from shk_widget rendering a value based on the wrong identifier when a TV held several product parameters.
Typical Pattern
[*param1:shk_widget=`select:param1:wraptag:first_selected`*]
Where Problems Start
- the TV stores several values in one field
- the widget expects one exact parameter key
- template markup assumes label and value are already normalized
What to Verify
- Check the raw TV value stored for the resource.
- Confirm the exact parameter name expected by
shk_widget. - Test the output with one product first before applying it to the full catalog.
Legacy ecommerce setups often fail not because Shopkeeper is broken, but because the data contract between the TV and the widget is loose. Once that contract is made explicit, the output becomes predictable again.
Building MultiPhotos Galleries in Evolution CMS
A practical introduction to using a MultiPhotos-style TV for gallery output in Evolution CMS projects.
Filtering Ditto Output by TV Values Without Losing Folder Control
How to combine Ditto filters, depth settings, and folder visibility rules when catalog data sits several levels deep.