Handling Pagination and Single-Image Output in EvoGallery

Gallery setups often need two different modes: paginated image lists and focused single-image output. Treat them as separate rendering tasks.

The EvoGallery question here was really about one dataset serving two different frontend behaviors.

Use Case One: Paginated Listings

[!EvoGallery? &paginate=`1` &show=`16`!]

This is the normal gallery mode: list a page of images and move through them in batches.

Use Case Two: Single Image Display

[!EvoGallery? &display=`single` &type=`single`!]

or, for simpler list output:

[!EvoGallery? &display=`images` &type=`simple-list`!]

The Important Point

These are not just cosmetic variations. A paginated gallery and a single-image view answer different UX needs, so the snippet call and template branch should reflect that difference directly.

Once a project tries to make one generic gallery call do everything, pagination and single-item behavior tend to interfere with each other. Splitting the modes cleanly is usually the better approach.

Newer post

Fixing Missing MultiTV Image Previews in the Manager

What to check when MultiTV stores the data correctly but image previews do not appear in the manager interface.

Older post

Using the `if` Snippet for Multiple Specific Resource IDs

How to handle a small set of specific resource IDs in Evolution templates without writing unreadable chains of conditions.