Weave Code
Cover Widget Laravel Package
friendsofvictoire/cover-widget
A responsive cover widget for Victoire CMS: drop it into any page to render a hero block with background image, overlaid heading, text, and link. Editors configure everything visually in the admin, with no custom templates or code required.
At a glance
Frequently asked questions about Cover Widget
- Is friendsofvictoire/cover-widget compatible with Laravel?
- No. It is a Symfony bundle (WidgetCoverBundle) built for Victoire DCMS and depends on Victoire's AbstractWidget, the Symfony DI container, Doctrine entities and Twig templates, none of which Laravel's service container, Blade compiler or Eloquent can hook into. There is no adapter layer, so installing it with Composer in a Laravel app will never give you a working widget.
- How do I install friendsofvictoire/cover-widget in a Laravel project?
- You effectively cannot. The bundle is registered through Symfony's AppKernel or bundles.php and its widget is registered in Victoire's widget registry, so there is no service provider or auto-discovery path Laravel would pick up. Any attempt ends at the Symfony 2.8/3.x and Twig 1.x version constraints, which will not resolve against a current Laravel install.
- What does the Victoire cover widget actually render?
- It renders a responsive hero block: a background image with overlay, a heading, body text and an optional link, all configured visually in the Victoire admin. The durable part is the Twig template and CSS, which amount to tens of lines of markup. Everything else in the bundle is Victoire-specific scaffolding for registration, forms and DCMS entities.
- Does friendsofvictoire/cover-widget support PHP 8 and Laravel 10 or 11?
- No. Version constraints sit in the Symfony 2.8/3.x and Twig 1.x era, and PHP 8 features such as typed properties and str_contains, plus Twig 3 runtime changes, are not accounted for. Composer will fail to resolve the bundle against modern Laravel, Symfony or PHP 8.x.
- What is the best Laravel alternative to a Victoire cover widget?
- Build a small Blade component such as <x-cover :image="..." :heading="..."> backed by a view composer or a cover_blocks Eloquent model. That gives you the same hero block with no legacy Symfony dependencies, and you can add a Filament or Nova form if editors need visual control. It is roughly a half-day to two-day task for a mid-level engineer.
- How do I port the cover widget markup to Blade?
- Extract the Twig template, CSS and any image-processing config into a reference directory, license permitting. Reimplement the markup as a Blade component, snapshot-test the rendered output, and add a responsive and accessibility pass that the original almost certainly lacks. Then remove the bundle from composer.json entirely and keep attribution if the license requires it.
- Is friendsofvictoire/cover-widget actively maintained?
- No. FriendsOfVictoire bundles have been dormant since roughly the Symfony 3 era, with zero stars, zero dependents and no release cadence. There is no active maintainer and no security disclosure channel, so you would be the first consumer in years.
- What dependency and security risks come with this bundle?
- Installing it drags legacy Symfony components and potentially unpatched Doctrine and Twig versions into your dependency graph. That is a supply-chain and CVE surface for a component that only renders an image and a headline. With no tests, no CI signal and no dependents, there is no field validation of any kind.
- Can I copy the Twig template and CSS into a commercial Laravel project?
- Possibly, but confirm the license first by checking the LICENSE file and repository before copying any assets into a commercial or redistributed product. Retain attribution if the license requires it. Treat the license question as a blocker to resolve before extraction, not after.
- Does this bundle work with Filament or Nova for editorial control?
- No. The editorial UI comes from Victoire's own widget form types and admin, which are Symfony and Twig based and have no relationship to Filament or Nova. If you need editorial control in Laravel, implement a Filament or Nova field on top of your own cover_blocks table instead.
Weaver
How can I help you explore Laravel packages today?