## 16.7.0

- The Secret Access Key and read-only password are no longer written into the Settings page. They were rendered back into their password inputs, which masks them on screen but leaves them readable in the page source. The fields now render empty and say whether a secret is stored; an empty field means "unchanged", and clearing one is explicit via a new "forget" checkbox. **If you have used an earlier version, treat your Secret Access Key as exposed and rotate it.**
- New "Recover lost registrations" tool on the Settings tab. Registration records each media's URL in its Dublin Core Source as well as in the plugin's own table; if that table loses rows — most often a database restored from a backup taken before the media was added — the photos stay in the gallery but the plugin no longer recognises them and their status shows as empty. This rebuilds those registrations from the Dublin Core Source, reporting separately any whose photo has left the gallery and so cannot be recovered. It checks before it writes, and runs in batches so it cannot time out.
- The plugin now ships en_UK and fr_FR translations. Previously every string fell through to its English key text, so a French gallery showed an English admin.
- Admin pages reworked: the four tabs share one stylesheet instead of each carrying a copy of the same rules; Settings is laid out in two columns with the maintenance tools beside the settings; S3 API help text is now hover icons rather than small print under every label; the plugin version has its own section; and the Migrate tab explains what migrating actually does.
- "Access Key ID" is relabelled "Access Key ID / Bucket name" — on Bunny Storage the Storage Zone name serves as both, which the old label did not convey.
- Fixed the Settings tab relying on the admin theme to provide jQuery for its buttons instead of loading common.js like the other tabs.
- Added `tools/verify-release.sh`, which checks that what the marketplace will package is really the tagged release (see the 16.6.0 note below).

## 16.6.0

- Media metadata (file size, and page count for PDFs) is now recorded when media is added, and shown on the photo page alongside the MIME type. The page count is read from the PDF's page tree over a byte-range request, so only the tail of the file is fetched rather than the whole document.
- A "Backfill metadata" button on the Settings tab fills in size and page count for media registered before that was recorded. It works in batches and loops until done, so it does not time out however many media exist.
- Metadata is stored in a new schemaless `meta` JSON column, added to existing installs by migration. Rows stay empty until the backfill fills them in.
- New "Debug logging" setting on the Settings tab. When on, the plugin logs what it is doing to the PHP error log and mirrors the same lines into the browser console on admin pages. Off by default.
- The Settings tab now shows the installed plugin version, read back from the plugin header so it cannot drift out of sync with the release.
- The bucket browser sorts folders and files alphabetically ignoring case, instead of the raw byte order S3 returns (which listed every capitalised name ahead of every lowercase one).
- Widened the bucket browser's Status column so longer statuses and error messages fit on one line.

## 16.5.0
- Media that was moved inside the bucket after being added is no longer offered for adding a second time. Registration records a media's full public URL, so moving the file (the usual "_incoming" to final-album shuffle) changed its URL and the bucket browser stopped recognising it — letting the same media be added again as a duplicate photo.
- Such a file is now matched on its filename, which survives a move, and shown as "already added (moved — URL is stale)" with a link to the existing photo. It cannot be selected.
- The duplicate check in the add path was extended the same way, so a moved media is also refused when added through the web-service API or a script, not just in the browser.
- When two registered media share a filename, the name is still treated as taken but no photo link is shown, so the status can never point at the wrong photo.
- Support shift-click range selection in the bucket browser.
- Stop reporting a reused photo as a registration failure.

## 16.4.0

- Deleting a photo can now delete the original from the S3 bucket too. This is off by default and enabled per install with the new "Delete originals fromS3" setting on the Settings tab; until it is turned on, deletion behaves exactly as before and the remote file is left in place.
- The remote file is only removed when it can be proved to belong to the bucket: the stored URL must resolve back to a key under the configured public URL base. Media whose URL points anywhere else is never touched.
- A file still registered to another photo is kept, so deleting one of two elements backed by the same original does not break the survivor.
- Deleting from the bucket requires the full Secret Access Key. The read-only password can no longer sign a destructive request.
- A bucket deletion that fails is reported on the admin page without interrupting the deletion — the photo has already left the gallery by then.

## 16.3.2 - 2026-07-30

- Fixed missing thumbnails on media registered by 16.3.1. That release made posters unique by appending bytes to the file after Piwigo had already recorded its checksum and size, leaving the database describing a file that no longer existed on disk and breaking derivative generation. Uniqueness is now supplied as a synthetic checksum passed to Piwigo, derived from the media URL, so the poster's bytes, size and dimensions stay truthful and re-adding the same media stays idempotent.

## 16.3.1

- Fixed registration failing with a duplicate-key error when several media shared the same poster image (typically the bundled placeholder). Piwigo deduplicates uploads by checksum, so identical posters collapsed onto a single photo; posters are now made unique before upload.
- Registration clears any leftover row for a reused photo id, so a media deleted without cleanup can no longer block a later add.
- Bucket listing failures in the "Add multiple" tab are logged to the browser console for debugging.

## 16.3.0 - 2026-07-30

- Renamed the plugin from `s3_video` to `s3_media`; existing installs are adopted automatically (config, media table, plugin registration).
- New media types beyond video: images, documents (PDF, office files) and books (EPUB & co), each with type-specific rendering on the picture page and bundled placeholder posters.
- New "Add multiple" tab: browse the S3 bucket and register selected files into an album.
- New "Migrate" tab: upload caddie originals to S3 (verified), register them as s3 media, and replace the local original with a poster.
- Bunny Storage folder listing now uses the native storage API, so folders the S3 gateway omits (empty ones, names the gateway chokes on) still show.
- Optional read-only password: enough for the Add multiple tab; only Migrate needs the full Secret Access Key. Secrets can now also be cleared from the Settings tab.
- Dublin Core integration: registration records the media URL as `dc_source` and its MIME type as `dc_format` when the Dublin Core plugin is active.
- Migrate failures are logged to the browser console for debugging.
- Admin layout rework: 50% left column, inline rows, fixed savebar.