Blog Sections Open

Building MultiPhotos Galleries in Evolution CMS

Before gallery workflows became more standardized, many Evolution projects used TV-driven image collections. The MultiPhotos approach solved a familiar need: attach several images to one resource and render them consiste

Before gallery workflows became more standardized, many Evolution projects used TV-driven image collections. The MultiPhotos approach solved a familiar need: attach several images to one resource and render them consistently on the frontend.

Why This Pattern Was Popular

  • editors could manage several images in one place
  • frontend templates stayed independent from raw TV storage
  • gallery layout could be changed without rewriting content

Implementation Shape

The typical helper read a JSON-like TV payload, looped through the stored image data, and rendered a row template inside an outer wrapper. That same idea still holds for modern gallery helpers: keep data parsing in PHP and keep markup in chunks or templates.

If a project still uses TV-based galleries, the most important rule is to separate storage, rendering, and image styling clearly so the gallery can evolve later.

Newer post

Adding a Simple Captcha Validator to FormIt

A compact FormIt pattern for generating a small custom captcha challenge and validating it through a custom validator.

Older post

Making shk_widget Render the Right Product Parameter

How to debug Shopkeeper parameter TVs when shk_widget outputs the wrong value or uses the wrong identifier.