- Can I install friendsofvictoire/slider-widget in a Laravel application?
- No. The package is a Symfony bundle for Victoire DCMS, not a Laravel package. It requires victoire/victoire and a Symfony kernel to boot, and it has no Laravel service provider, facade, config publish, or Blade views. Composer installation alone will not make it usable in Laravel.
- Is friendsofvictoire/slider-widget a Laravel Composer package?
- No. Despite the vendor-style Composer name, the repository FriendsOfVictoire/WidgetSliderBundle is a Symfony bundle that adds a slider widget to Victoire CMS. Its integration points are Symfony dependency injection, Twig templates, Doctrine entities, and Victoire widget registration. Laravel's service providers, Blade, Eloquent, and Livewire or Inertia have no mapping to those extension points.
- Which Laravel versions does friendsofvictoire/slider-widget support?
- None are supported. There is no Laravel service provider or package discovery entry, so Laravel will not register the bundle. The package targets a Symfony 2.8/3.x-era Victoire CMS runtime, not Laravel 5 through 11. Do not treat it as a Laravel slider component.
- How do I install and configure friendsofvictoire/slider-widget?
- In a Victoire or Symfony application you would install it with Composer, enable the bundle in the Symfony kernel, and register or configure the widget through Victoire. There is no Laravel config file to publish and no Blade view to render. Before any work, confirm that the Packagist package friendsofvictoire/slider-widget is the canonical distribution because the repository name is WidgetSliderBundle.
- What PHP and Symfony versions are required by friendsofvictoire/slider-widget?
- The evaluation notes a 2018 Symfony bundle that pins Symfony 2.8/3.x and likely PHP 5.6 to 7.2 constraints. Those runtimes are end-of-life. Composer will likely refuse to resolve against PHP 8.x without overriding EOL framework constraints, which is unsafe because it can inherit unpatched CVEs.
- Is friendsofvictoire/slider-widget maintained and safe for production?
- No. The last release is dated 2018-06-07, with one star, zero dependents, and no evidence of maintainers, issue triage, or security response capability. That is a high abandonment and security risk for production. Have legal review any unmaintained dependency before use.
- Can I run Victoire headless and use this slider widget from Laravel?
- You can keep Laravel as the main application and run Victoire as a headless backing service that renders or serves the widget over HTTP. That avoids an in-process Symfony bundle integration, but you still inherit an EOL CMS, its Doctrine, Twig, and Symfony dependency tree, and two runtimes to operate. For a slider specifically, this is usually more cost than value.
- What should Laravel developers use instead of friendsofvictoire/slider-widget?
- Reimplement the slider in Laravel with a Blade component or Livewire component and a maintained JavaScript slider library such as Swiper, Splide, or Glide. The original package's value is the Victoire widget binding, not the slider behavior itself. A clean Laravel implementation is lower risk and easier to test than bridging an abandoned Symfony bundle.
- How should I test a Laravel slider if I cannot use this package?
- Do not try to test the Symfony bundle inside Laravel; without a Symfony kernel and Victoire it cannot boot. Instead, write Laravel feature tests for the data model, validation, ordering, translations, and rendered Blade output, then use browser tests for responsive behavior and accessibility. Treat the original bundle only as a reference for field schema and behavior.
- What is the migration path from friendsofvictoire/slider-widget to Laravel?
- There is no in-place migration. Run a short spike to catalogue what the widget actually does, including image, caption, link, alt text, ordering, responsive configuration, translation handling, and Twig markup, then map that schema onto a Laravel model or JSON column and rebuild the UI with Blade and a JavaScript slider. The durable output of evaluating the package is the specification, not a reusable Laravel dependency.