Blog Sections Open
Handling Multiple Image Size Options in Shopkeeper Product Variants
Shopkeeper stores often need one product page to represent more than one purchasable size or image format.
The source question described a Shopkeeper product that had more than one size variant, including large and small dimensions such as 300x300 and 20x20. That is a familiar Shopkeeper problem: one visual product, several practical options.
What to model separately
- the public product page and marketing description
- the option list shown to the user
- the values that affect ordering or price
- the images used to represent each option, if they differ
What to avoid
Do not hide too much option logic inside one overloaded TV string. That becomes hard to validate, hard to render consistently, and hard for editors to update without mistakes.
A cleaner pattern
Use a clear option model: one stable product resource, one structured source for the size variants, and one rendering layer that knows how to output the selected variant cleanly in Shopkeeper. The moment the options start driving price, image choice, and order payloads, the project benefits from a more explicit data structure.
Enabling Captcha in JotX Comment Forms
A small but useful JotX configuration note: how to enable captcha in moderated comment flows to reduce automated spam on legacy Evo sites.
Making FormIt Work with Custom Frontend Markup
How to fix a FormIt form that looks correct in the template but never submits the values you expect because the field names and submit flow are incomplete.