- What is friendsofvictoire/listing-widget used for?
- It is a configurable listing widget for Victoire DCMS, a Symfony-based CMS with a widget and page-builder composition model. It lets editors add template-driven, curated lists of content to pages with minimal setup. The functional surface is small: query content and render a configurable list, likely as a thin Twig template over a Doctrine query. It is not a standalone library and is not intended for Laravel.
- Is friendsofvictoire/listing-widget a Laravel package?
- No. Despite being framed as a Laravel or PHP package, the repository name and FriendsOfVictoire\WidgetListingBundle namespace show it is a Symfony bundle for Victoire DCMS. It uses Symfony's container, Twig templating, Doctrine persistence, and Victoire's widget registration rather than Laravel's container, Blade, and Eloquent. There is no direct fit with a Laravel stack.
- Can I use friendsofvictoire/listing-widget with Laravel 10 or 11?
- No. It is a Symfony and Victoire bundle, so Laravel version support is not applicable and it should not be added to a Laravel composer.json. The extension mechanism, templating, and persistence idioms are all different from Laravel. For a Laravel application, use it only as a design reference and reimplement the listing behavior natively.
- What Symfony and PHP versions does friendsofvictoire/listing-widget support?
- The provided context does not state exact constraints, but a bundle last released in May 2019 likely targets Symfony 3.x or 4.x and PHP 7.x. You should inspect composer.json and run a resolved constraint audit before assuming compatibility with Symfony 5.4, 6.x, or 7.x. Expect a binary outcome: freeze your framework version or patch the bundle.
- How do I install friendsofvictoire/listing-widget?
- Installation is intended for a Symfony application running Victoire DCMS, not a generic PHP or Laravel app. You would add it with Composer, register the bundle, and rely on Victoire's widget registration and rendering pipeline. Validate the dependency constraints and license terms first, and exercise the widget end to end in an isolated Victoire instance before committing.
- Does friendsofvictoire/listing-widget work without Victoire CMS?
- Almost certainly not. It is a plugin that depends on Victoire's widget registration, entity model, and rendering pipeline, so it is not standalone even on Symfony. The integration cost outside a full Victoire install is likely higher than the value of the widget itself. Confirm by checking the service registration and trying it in a minimal Victoire setup.
- Is friendsofvictoire/listing-widget still maintained?
- No. The last release was 2019-05-27, with 2 stars, 0 dependents, and a score of 0.13, and Victoire DCMS itself is quiet. There is no upstream security patch path, and the effective maintainer becomes you if you adopt it. Treat it as unmaintained and plan accordingly.
- Does friendsofvictoire/listing-widget have test coverage, and should I fork it?
- There is no evidence of test coverage, so the cost of owning it forward is unmeasured. Forking is defensible only if you are already committed to Victoire; it requires patching version constraints, adding tests, pinning dependencies, documenting the fork, and setting a replace-by date. For any other stack, reimplementing natively is the cheaper and safer path.
- What are the best Laravel alternatives for a configurable listing widget?
- In Laravel, build the feature natively using Eloquent queries plus Blade or Livewire rather than pulling in a Symfony bundle. The core behavior, rendering a configurable list of curated content, is only a few hundred lines and carries no unique intellectual property. If you need a page-builder model, evaluate actively maintained Laravel CMS or admin packages instead.
- What production risks should I check before depending on friendsofvictoire/listing-widget?
- Expect high technical risk: a 2019 bundle with no releases in over six years, no security patch path, likely Symfony 3.x or 4.x and PHP 7.x ceilings, and a dormant underlying platform. There is also an unmeasured fork cost because test coverage is not evident. Run a version-constraint, license, and advisory audit before anything else, and avoid it entirely for new Laravel builds.