elgentos / magento2-imgproxy-prismic-support

elgentos/magento2-imgproxy-prismic-support

Integration between Elgentos Imgproxy and Prismic IO modules for Magento 2

  • elgentos ecommerce solutions
magento2-module Compatibility: 2.4.8 Code Quality: Fail Tests: N/A Security: Pass MIT

elgentos/magento2-imgproxy-prismic-support

Integration module that connects the elgentos/magento2-imgproxy and the elgentos/magento2-prismicio extensions for Magento 2.

What it does

Automatically transforms Prismic CDN image URLs through imgproxy before rendering, with the main goal of Prismic API usage reduction.

These are also benefits, but these are also handled by Prismic (which uses Imgix internally);

  • On-the-fly image optimization
  • Responsive image sizing
  • Format conversion (WebP, AVIF)
  • Bandwidth savings

Requirements

  • PHP 8.3+
  • Magento 2.4+
  • elgentos/magento2-imgproxy - installed and configured
  • elgentos/module-prismicio - installed and configured

Installation

composer require elgentos/magento2-imgproxy-prismic-support
bin/magento setup:upgrade
bin/magento cache:flush

Configuration

No additional configuration needed. The module:

  1. Respects imgproxy enable/disable setting
  2. Automatically detects Prismic image blocks
  3. Transforms URLs before rendering

Scope

Supported:

  • Standalone Prismic Image blocks (Elgentos\PrismicIO\Block\Dom\Image)

Not supported:

  • Images embedded in RichText blocks (different rendering pipeline)

How it works

The module uses a BEFORE plugin that:

  1. Intercepts Elgentos\PrismicIO\Block\Dom\Image::fetchDocumentView() before it renders the HTML
  2. Checks if imgproxy is enabled
  3. Retrieves the image context (URL, width, height)
  4. Transforms the URL through imgproxy's getCustomUrl() method
  5. Modifies the context URL in-place
  6. Allows the original method to proceed with the transformed URL

This ensures all standalone Prismic images are optimized through imgproxy without any template modifications.

Troubleshooting

Images not transforming

  1. Verify imgproxy module is enabled and configured:

    bin/magento module:status | grep Imgproxy
    
  2. Check if imgproxy is enabled in system configuration:

    • Admin > Stores > Configuration > Imgproxy > General > Enabled
  3. Check logs for transformation errors:

    tail -f var/log/system.log | grep IMGPROXY-PRISMIC
    

Inspect rendered HTML

To verify URL transformation is working:

<!-- Before (original Prismic URL): -->
<img src="https://images.prismic.io/example/image.jpg" alt="..." width="800" height="600" />

<!-- After (imgproxy transformed URL): -->
<img src="https://imgproxy.example.com/[signature]/resize:fit:800:600/plain/https://images.prismic.io/example/image.jpg" alt="..." width="800" height="600" />

Enable debug logging

The module logs all transformations and errors with the [IMGPROXY-PRISMIC] prefix. Errors are logged at the ERROR level, so check:

grep IMGPROXY-PRISMIC var/log/system.log

Architecture

  • Plugin Type: BEFORE
  • Target: Elgentos\PrismicIO\Block\Dom\Image::fetchDocumentView()
  • Dependencies: Config and Image model from elgentos/magento2-imgproxy

The BEFORE plugin intercepts the method before HTML rendering, allowing clean URL transformation by reference modification of the context object.

License

MIT

Support

For issues or feature requests, please contact [email protected]

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
1.0.1 stable Fail Magento 2.4.8 Details 2026-05-12 13:29:27
1.0.0 stable Not tested Not yet tested Details 2026-01-19 09:03:51

Requires 4

Package Constraint
php ^8.3
elgentos/magento2-imgproxy *
elgentos/module-prismicio *
magento/framework *

Compatibility

Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 not tested Pass
2.4.8 Pass Pass
2.4.9 Fail di error Fail di error

Code Quality

Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.

Static analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

Static analysis results
Tool Status Findings Summary
PHPCS Pass 0
PHPMD Pass 0
Cpd Pass 0
Composer validate Info 3 valid; 3 advisory notes (composer validate --strict)

PHPStan

Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A 58
2.4.8 58 58
2.4.9 61 61

Tests

Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.

Unit tests

Unit tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Integration tests

Integration tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Security

Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0
License
MIT
Authors

More from elgentos

View vendor
Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.