Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Search Widget

Search Widget Laravel Package

friendsofvictoire/search-widget

A Symfony bundle that adds a search widget to the Victoire CMS, letting editors drop a configurable site search form into any business page. Ships Twig templates and widget configuration hooks you can wire to your own search backend or index.

View on GitHub
Deep Wiki
Context7

At a glance

Frequently asked questions about Search Widget
Can I install friendsofvictoire/search-widget in a Laravel application?
No. The package is WidgetSearchBundle, a Symfony bundle built for Victoire DCMS, and it integrates through Symfony's dependency injection container, Twig templating, and the Victoire widget system. There is no service provider, facade, config file, or Laravel package discovery metadata, so Composer cannot wire it into a Laravel app. Requiring it would only pull in an unmaintained Symfony dependency tree.
Is friendsofvictoire/search-widget a Laravel package or a Symfony bundle?
It is a Symfony bundle. The repository is FriendsOfVictoire/WidgetSearchBundle, and every integration point it exposes is Symfony-specific. If your intake record lists this as a Laravel package, the record is wrong and should be corrected before any evaluation continues.
What PHP and Symfony versions does friendsofvictoire/search-widget support?
It is a Symfony 2.8/3.x-era bundle that pins Twig 1/2 and PHP 7.x constraints. Modern Symfony 6/7 and PHP 8.2+ runtimes will almost certainly fail Composer resolution, and the exact declared ranges should be confirmed by reading its composer.json. There is no Laravel version support of any kind because it is not a Laravel package.
How do I install and register the search widget in a Symfony Victoire project?
You would composer require the bundle, register it in the Symfony kernel, and then enable and configure the widget slot on a Victoire business page. The bundle ships Twig templates you can override or theme to match your site. This workflow only applies if the application is already running Victoire DCMS or a surviving fork of it.
What search backend does the Victoire search widget actually query?
That is not visible from the package name or description, and it matters before you assign any value to it. A Victoire widget is typically thin presentation glue that renders a form and hands the query to a Victoire core service or to your own index. Determine whether the backend is a database LIKE query, Solr, Elasticsearch, or something internal before assuming the bundle provides working search.
Is friendsofvictoire/search-widget actively maintained?
There is no meaningful maintenance signal: zero stars, zero dependents, no visible maintainer activity, no CI badge, no test suite, and no release cadence. Victoire DCMS itself has been largely dormant for years, and the bundle inherits that lifecycle risk. There is also no security policy, so there is no advisory response path for its pinned dependencies.
What should I use instead of this package in a Laravel application?
Use Laravel Scout with Meilisearch or Typesense for good faceting with low operational overhead, or Algolia if you prefer a managed-first service. Build the presentation layer as a Blade component or a Livewire widget with debounced input, result highlighting, and pagination. Put the backend behind a SearchProvider interface so it stays swappable, which is the long-term value the Symfony bundle would never have given you.
Does friendsofvictoire/search-widget support Laravel package auto-discovery or facades?
No. There is no extra.laravel block in composer.json, no ServiceProvider class, and no config directory in the Laravel sense. Symfony bundles are registered explicitly in the kernel, and the bundle's widget configuration hooks are a Victoire concept with no Laravel equivalent. Anything resembling auto-discovery would have to be written from scratch.
How hard is it to migrate an existing Victoire search widget to Laravel?
Treat it as a rewrite, not a port. Keep the existing Twig widget as presentation-only and route all queries through a service interface so you have a clean swap point when Victoire is retired. Then build a Laravel-native equivalent in roughly three to five engineer-days, and budget two to four more if you instead try to fork and modernise the Symfony bundle.
How can I test the widget's search behavior before adopting it?
You largely cannot, because the repository ships no test suite and no CI pipeline to demonstrate correctness. The only thing you can verify directly is the Twig render path, which is presentation rather than search logic. Any real confidence in relevance, ranking, or filtering would require writing your own integration tests against the backend the widget delegates to.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
diephp/sequences
users-au/socialite-provider
twidpay/twid-logger
mrnewport/laravel-plaid
mrnewport/laravel-repo
mrnewport/laravel-docsign
mrnewport/laravel-stow
mrnewport/laravel-flow
mrnewport/laravel-priceable
mrnewport/laravel-nestedterms
fredmeng/laravel-apidoc-generator
itstructure/laravel-multilingual-tools
pdustdar/elasticsearch
markupai/php-sdk
rlacerda83/lumem-microservice-shipment
uni-method/symfony-lib
tacticmedia/scim-server-bundle
neika-ai/symfony-bundle
mattleads/agent-publishing-bundle
glavweb/framework-bundle