Product guide
imgproxy Media Connector
Mirror WordPress image originals and variants to S3-compatible storage and serve signed imgproxy transformations while retaining local files.
- Published version
- 1.2.5
- Compatibility
- WordPress 6.3 minimum ; 6.3 et 7.1.3 recettés, PHP 7.4 minimum ; 7.4, 8.3 et 8.4 recettés, imgproxy 4.0.17 recetté, Garage 2.3.0 compatible S3 recetté
- Product page (French)
- Connecteur médias imgproxy
Prerequisites
| Component | Requirement |
|---|---|
| WordPress | 6.3 or newer |
| PHP | 7.4 or newer |
| Storage | An S3-compatible bucket controlled by the merchant |
| Transformation | An imgproxy 4.x service with signing key, salt and bucket access |
Novelience supplies the connector, not an S3 or imgproxy hosting service. You provide and secure those services. WooCommerce is not required. The plugin interface has English source strings and a bundled French translation.
Installation
Back up your WordPress database and installed plugin files. Keep the previous ZIP and test restoration before changing a live shop.
In the Novelience customer area, open Mes produits et licences (My products and licences). Download imgproxy-media-connector-1.2.5.zip (version 1.2.5) and compare its SHA-256 with the product page: b3d98078f179f5f13c193edf8de4b7683fa3bb9dc85267304da4fed3c0e6d657.
In WordPress, open Plugins › Add New › Upload Plugin, select the ZIP, and activate it. For an update, choose to replace the existing plugin in place; do not uninstall the old version first.
Check existing settings and run the product-specific checks below on your own theme, checkout and integrations.
Provision the bucket and imgproxy independently. Configure the storage endpoint, bucket, region and credentials, plus the public imgproxy URL, signing key and salt, in Settings › imgproxy media or through deployment configuration.
Run the built-in connection diagnostic. Upload a synthetic image and inspect the original and generated variants in storage. Confirm a signed imgproxy URL returns a transformed image.
Edit the image and verify that new variants are mirrored. Upload a non-image document and confirm that it stays outside this image transformation path.
Configuration
Supply your own S3-compatible storage and imgproxy service, then configure endpoint, bucket, credentials, signing key and salt. Test the connection and a real transformed image.
Usage
Upload and edit a synthetic image, inspect mirrored originals and sizes, and load a signed transformed URL. Check that non-image documents remain on their normal WordPress path.
Update and rollback
Back up WordPress files, database and configuration before replacing the ZIP in place. Confirm the diagnostic, signed URLs and local originals after updating. If services fail, disabling the connector restores local URLs on newly rendered pages; clear page caches as needed. A code rollback does not restore remote objects, so retain an object-store backup and check lifecycle rules separately.
Limitations
- WordPress keeps local originals, metadata and generated files. The connector mirrors images and does not remove local media after upload.
- If configuration is incomplete or an original could not be mirrored, the original local URL is used.
- Once an image is mirrored, a signed URL is produced without checking remote service health on each page render. A later storage or imgproxy outage can break that signed URL until the service recovers.
- Documents and other non-image attachments are not transformed. Test your CDN, cache, object lifecycle and delete behavior on your own setup.
Published version
| Field | Current direct release |
|---|---|
| Version | 1.2.5 |
| ZIP | imgproxy-media-connector-1.2.5.zip |
| SHA-256 | b3d98078f179f5f13c193edf8de4b7683fa3bb9dc85267304da4fed3c0e6d657 |
The ZIP named above is the current Novelience direct release. A Woo Marketplace or WordPress.org package, if any, has its own review and publication state.
Support
Need help with installation or setup?
Written support is available in English and French.