Weave Code
Ezenhancedimageassetbundle Laravel Package
novactive/ezenhancedimageassetbundle
An eZPlatform/Ibexa bundle adding an enhanced image field type with focus point selection, default image configuration for file size optimization, lazy and progressive loading, retina and WebP variations, and Twig render field parameters.
At a glance
Frequently asked questions about Ezenhancedimageassetbundle
- Can I use novactive/ezenhancedimageassetbundle in a Laravel application?
- No. This is a Symfony bundle for Ibexa DXP (formerly eZ Platform), registered in the kernel bundle array and wired into Ibexa internals such as the field type registry, the image variation handler and siteaccess-aware parameters. It ships no Laravel service provider, no publishable config and stores its data in Ibexa tables like ezcontentclass_attribute and ezcontentobject_attribute. For a Laravel codebase, evaluate Intervention Image or Glide with a custom focus-point crop instead.
- What are the requirements and supported Ibexa and PHP versions?
- The bundle requires Ibexa 5 and PHP 8.3. It extends the native ezimage field type, so it must run inside an Ibexa installation whose variation and asset pipelines are already in place. There is no Laravel or standalone Symfony support path.
- How do I install and register NovaeZEnhancedImageAssetBundle?
- Run composer require novactive/ezenhancedimageassetbundle, then add Novactive\EzEnhancedImageAssetBundle\EzEnhancedImageAssetBundle to the registerBundles() array in your kernel. After registration you still need to update image variation configuration to use the focusedThumbnail filter and wire the enhancedimage-css and enhancedimage-js Encore entries into your admin theme.
- What does the enhancedimage field type actually do?
- It adds an enhancedimage field type that extends the standard ezimage type with focus point management. Editors pick a focal point on the uploaded image in the admin UI, and generated variations then crop around that subject rather than the image center. This is useful for portraits, product shots and editorial imagery where the subject is off-center.
- How do I configure image variations to crop around the selected focus point?
- Rewrite your image variation configuration so the relevant aliases use the focusedThumbnail filter instead of the default centered crop. Because the configuration is siteaccess-aware, you can define different defaults per siteaccess along with default image post-processors. Test each alias after the change, since aliases that still use centered cropping will silently ignore the focus point.
- How do I migrate existing ezimage fields to enhancedimage?
- The documented migration is raw SQL UPDATE statements against Ibexa core tables, changing data_type_string from ezimage to enhancedimage on the relevant class and object attribute rows. Because the new type extends the old one, underlying storage stays byte-compatible and the change is reversible. The provided statements have no idempotency, no transaction wrapper and no rollback script, so take a backup, wrap the change in an explicit transaction and rehearse it on a copy of production first.
- Does it support retina and WebP variations, and what is the storage impact?
- Yes, the bundle generates retina and WebP variations alongside regular ones. Each alias can spawn a _retina variant and a WebP variant, which means up to four times the storage and cache entries per image per alias, and focus-point crops reduce cross-image alias reuse. Historically, retina and focus point interaction has been buggy, so test focus, retina and WebP combinations hardest.
- Which post-processor binaries need to be installed on my servers?
- You need the post-processor binaries available on every node that generates images, typically pngquant, jpegoptim and cwebp for the optimization and WebP steps. A past release fixed placeholder generation failing when no post-processors were configured, so verify behavior in environments where binaries are missing. Provision them in your image build or container image rather than relying on ad hoc installs.
- How do lazy and progressive loading and the Twig render field parameters work?
- The bundle provides lazy and progressive loading support plus extended Twig render field parameters so templates can control how the enhanced image is rendered. Parameter names and usage are documented in the bundle's .md files and in the packaged documentation site rather than in the README. Check the docs for your exact pinned tag, since the parameter surface has changed across releases.
- Where do I report bugs, and how stable is the package for production?
- This repository is a read-only subtree split of one directory of Novactive/Nova-eZPlatform-Bundles, so issues and pull requests must go upstream to the vendor monorepo. Adoption is very low, there are no dependents, and release notes are stubs that mostly link to diff comparisons, which makes the risk delta between tags hard to judge. Pin a specific tag only after obtaining the real diff, confirm whether fixes land on the 4.x line or the 3.x line first, and check whether a commercial support path exists with Novactive.
Weaver
How can I help you explore Laravel packages today?