Photo Galleries

The problem, in one sentence

A product page exists to sell. It takes five or six photos, not forty. Yet those forty photos exist, they are useful, and they sit on your hard drive because nowhere suits them.

Filing and publishing

• Folders and sub-folders, as many levels as you need.
• Batch upload, with a caption for each photo.
• Ordering by drag and drop, or by typing a rank.
• A cover photo for each folder.
• Tags on folders, so your visitors can filter the list themselves.

Linking photos to the catalogue

A folder can be attached to one or several products: those product pages then show a link to the folder. A single photo can also be linked to a product and appear on its page. And a gallery can be linked to nothing at all, and stand on its own.

Image handling, done properly

• Four variants generated automatically: a phone does not download the desktop version.
• Photos taken on a phone are straightened from their recorded orientation.
• Hidden file data — including GPS coordinates — is stripped before publication.
• WebP output, lighter than JPEG, wherever the server can produce it.

Fixing a photo without leaving the shop

You are browsing your gallery, logged into the admin, and you spot a crooked photo. You do not write down its name to find it later: you fix it right there.

On hover, every photo carries two buttons. The pencil opens a panel in place:

• Rotate — a quarter turn left, right, or a half turn.
• Crop — you draw the area to keep with the mouse, and confirm.
• Replace the file — caption, rank, album, cover and linked product are kept. Only the image changes.
• Back to the original — this button only appears on a photo already retouched.

The bin deletes the photo and its files, after confirmation. All three sizes are rebuilt automatically: nothing to relaunch.

The same panel exists in the admin, on every thumbnail of the Photos screen.

Nothing is lost. Before a photo is retouched for the first time, its original file is set aside and never touched again. “Back to the original” restores day one, not the state before the last operation.

And a visitor sees none of it

These buttons are not hidden by a stylesheet: they are not sent at all. Neither the buttons, nor the panel, nor the script that drives them.

Before any write, four locks are checked in order: the request must be a form submission, the employee must be logged into the admin with an account still active, their profile must hold the matching permission — these are PrestaShop's own permissions, not something the module invented — and a module-specific token, derived from the shop's secret key and the employee's id, must match. Preview mode alone grants no write access whatsoever.

The sharpening setting

Shrinking a photo always softens it a little. An unsharp mask makes up for that, with a slider: zero to do nothing, sixty by default, beyond a hundred and twenty strong edges start to show a halo.

It only applies to reductions — sharpening an enlargement would merely amplify the blur.

A careful presentation

A grid where the visitor sets the number of columns, with three sizes to choose from. A full-screen viewer with navigation, slideshow, download and send-to-a-friend. An optional block on the home page.

Your customers can fill a folder

Hand a folder to a customer: they upload their photos from their account, and you approve or reject each one from a dedicated screen. It is the customer-builds gallery, without you receiving attachments by email.

Protecting your work

• A copyright line burned into displayed images — never into the original archive.
• A folder marked protected: search engines no longer index its images, the viewer stops at medium resolution, downloading is refused, right-click and drag are blocked.
• Displaying your images from another site can be forbidden.

Prepare without publishing

An unpublished folder stays invisible to your visitors. A private preview link still lets you review it in real conditions, from a phone or by someone else, without putting the shop into maintenance.

Keeping the library in order

Regenerate thumbnails, shrink archives, delete files left on disk with no matching photo. All three exist in the interface and on the command line.

One entry, not one per language

Album titles and captions are entered once and shown as they are to every visitor: the module does not keep a version per language. On a multistore installation, the library is shared across shops.

What it does not do

It is not an image bank, nor a file manager, nor a retouching tool. It files, it protects, it displays.

What protects your shop

No network call when a page is displayed. Images are served as ordinary files. The module cannot cause a 504 error: it never waits for anyone.

What you get, depending on your shop

This module comes in 2 versions, one per major PrestaShop release. You get them all: one purchase, one licence, and you pick the file when you download.

• Version 2.1.5 — PrestaShop 9.0.0.0 to 9.99.99, PHP 8.1 or above.
• Version 1.8.0 — PrestaShop 1.7.0.0 to 8.99.99, PHP 7.1 or above.

Your customer account lists every version with its limits spelled out, and highlights the one matching your shop. Nothing stops you taking the other: if you are preparing a migration, or working on several sites, it is there, on the same licence.