Blog Sections Open
Making `paramEditFull` Work with `shk_widget` in Shopkeeper
If Shopkeeper parameter editing works in one mode but not in another, the issue is usually in how values are encoded and passed into the rendering helper.
Shopkeeper parameter editing can become tricky when several helper layers are mixed together. The legacy case here involved paramEditFull, a TV-based parameter field, and output through shk_widget.
The Common Pattern
One helper renders and edits a parameter list, while another helper expects a very specific value format. If the stored data and the widget expectations drift apart, the output starts looking wrong even though the parameter technically exists.
Practical Rule
When Shopkeeper parameter tools disagree, inspect the value format end-to-end: how the TV stores it, how the edit helper rewrites it, and how the final widget expects to receive it. Most breakages come from format mismatch rather than from a missing parameter.
Using WebLoginPE with Administrator-Approved Registration
How to think about moderated registration flows where users apply first and an administrator approves the account later.
Troubleshooting KCFinder Path Problems in Older Evolution Builds
A practical note on KCFinder issues caused by path settings, MCPUK integration, and mismatched base path assumptions.