Weave Code
Layouts Remote Media Laravel Package
netgen/layouts-remote-media
Netgen Layouts Remote Media adds remote media support to Netgen Layouts, letting editors fetch, manage, and render externally hosted media within layout blocks. A PHP package for flexible, reusable media content in Layouts-powered sites.
Netgen Layouts & Remote Media integration
Frequently asked questions about Layouts Remote Media
- Can I use netgen/layouts-remote-media in a Laravel application?
- No. Despite being described as a PHP package, this is a thin Symfony bundle that bridges Netgen Layouts and Netgen Remote Media, with no Laravel service provider, facade, or config integration. It assumes Netgen Layouts core, its block-definition model, and its rendering pipeline are already present in the host application. If your stack is plain Laravel, this package is not applicable and you should look at Laravel-native media or DAM packages instead.
- How do I install and configure netgen/layouts-remote-media?
- Run composer require netgen/layouts-remote-media, then register the bundle in your Symfony kernel as you would any other bundle. You must also have netgen/remote-media installed and configured with at least one provider plus valid API credentials. After that, build or override the block templates used to render the remote media items inside your layouts.
- What are the prerequisites before adopting this package?
- You need an existing Symfony application running Netgen Layouts, Netgen Remote Media, and the Ibexa or eZ Platform version those two support. The package contributes only block definitions and handlers, so it inherits storage, admin UI, and provider SDKs entirely from its upstreams. Teams not already on Layouts should not treat this as a starting point; it presupposes the whole composition layer is in place.
- Which versions of Netgen Layouts, Remote Media, and Ibexa are compatible?
- The package has to track the majors of both Netgen Layouts and Netgen Remote Media, and transitively the Ibexa version those support. That creates a three-way compatibility matrix maintained by a single vendor, so confirm the exact tested version triple with Netgen before committing. If you are on an older Ibexa release, you may need to upgrade first.
- Is netgen/layouts-remote-media actively maintained, and what community support exists?
- Adoption signal is very low: the repository shows zero stars and zero dependents, so there is essentially no community backstop such as third-party bug reports, forks with patches, or Stack Overflow answers. Maintenance depends on Netgen's internal priorities, and small vendor packages like this are often released once and patched on request. Ask the vendor directly about release cadence relative to Layouts core, and budget for carrying your own patches.
- Does it support custom or self-hosted DAM providers, or only SaaS sources like Unsplash?
- The provider abstraction comes from Netgen Remote Media rather than this package, so support for a custom or self-hosted DAM endpoint depends on what Remote Media offers. Bundled providers typically cover services such as Unsplash, Pexels, and Pixabay, with a custom endpoint option for internal systems. Verify against your Remote Media version whether a custom provider can be registered for your internal DAM before designing around it.
- Are remote media URLs resolved at render time or cached and persisted?
- This is not clearly documented, so treat it as an open question for the vendor or a spike. Any design that resolves provider URLs during page render inherits the provider's uptime, latency, and rate limits, which is a real production risk. If resolution happens at render time, plan a caching layer or a local proxy so page performance is not tied to a third-party API.
- What happens when a remote asset is deleted or revoked at the provider?
- The package does not appear to define explicit behavior for deleted, revoked, or re-licensed remote assets, so this needs testing. Decide whether editors should see a graceful placeholder or a hard error, and make sure your block templates handle a failed lookup. Provider lifecycles change without notice, and this package cannot shield you from assets disappearing.
- Are image variations and derivatives generated locally or by the provider's transform API?
- Derivatives are most likely delegated to the provider's transform or resize API rather than generated locally, since the package ships no image processing layer of its own. That affects your CDN strategy, cache invalidation, and per-transform API costs at the provider. Confirm the behavior for each provider you enable and check whether local caching of transformed URLs is possible.
- What license is netgen/layouts-remote-media under, and can I use it in a proprietary product?
- The package is GPL-2.0, the same license as Netgen Layouts core, so this is usually already a settled question for shops on the Layouts stack. It is fine for GPL-compatible applications, but a proprietary distribution model requires legal review. Because Layouts core carries the same license, adopting this package is unlikely to change your existing licensing position.
Weaver
How can I help you explore Laravel packages today?