Weave Code
Search Bundle Laravel Package
liip/search-bundle
LiipSearchBundle integrates Zend Lucene search into Symfony applications, offering services to build indexes, run queries, and manage results. It provides a simple, configurable way to add full-text search to your project.
This bundles provides some basic infrastructure for creating a search UI in Symfony2 applications along with integration with Google's search API
Frequently asked questions about Search Bundle
- Is liip/search-bundle compatible with Laravel?
- No. LiipSearchBundle is a Symfony bundle: it assumes bundle registration in a Symfony kernel, DI container compilation, service tagging and the Symfony event dispatcher. Laravel has none of those seams, so there is no supported way to boot it inside a Laravel application. Bridging the two would mean rewriting the bundle internals, at which point the package adds nothing.
- Can I install liip/search-bundle in a Laravel project with Composer?
- Composer may resolve it if you relax platform requirements, but the releases target PHP 5.x and Symfony 2.x, so composer why-not will normally surface constraint conflicts on PHP 8. Even with patched constraints you hit removed language features and Symfony 2 APIs. Getting the files into vendor/ is not the same as getting a working service, and the package ships no Laravel service provider.
- Is LiipSearchBundle still maintained?
- No. The upstream repository is archived and read-only, the last release was on 2016-07-22, and there are no security advisories or maintainer responses. It has roughly 34 stars and zero dependents, so there is no community to absorb patches. Treat it as abandoned.
- What search backend does LiipSearchBundle actually wrap?
- Despite being described as a generic search abstraction, its remote backend is a thin wrapper around the Google XML/SOAP Search API, which Google deprecated and discontinued. Zend Lucene index services are also referenced in its documentation, but neither path gives you a maintained, framework-agnostic search layer today. There is no configuration in which it returns live results for a modern Laravel app.
- Does LiipSearchBundle work with PHP 8, Symfony 6 or Symfony 7?
- No. The package targets PHP 5.x and Symfony 2.x and is not compatible with Symfony 6 or 7. Running it on PHP 8 would require you to patch the codebase yourself, and because the repository is archived there is no upstream path to support. Current Laravel versions require PHP 8.1 or newer, which rules it out outright.
- What is the best Laravel alternative to LiipSearchBundle for site-local search?
- Use laravel/scout. The database driver is fine for small datasets, and the Meilisearch or Typesense drivers add relevance ranking, typo tolerance and faceting when you outgrow it. Scout is first-party, actively maintained, and integrates with Eloquent without any Symfony coupling.
- How do I add full-text search to Eloquent models in Laravel?
- Install laravel/scout, apply the Searchable trait to the model, and choose a driver in config/scout.php. Model::search('term')->where('status', 'published')->paginate(15) returns an Eloquent-style builder over the results. Index updates can be queued so writes stay fast in production.
- How do I replace the Google web search feature LiipSearchBundle provided?
- Call the Google Custom Search JSON API directly through Laravel's Http facade, store the API key and search engine id in config/services.php, and cache responses to protect your quota. This is typically about 50 lines of code and is straightforward to test with Http::fake(). No Composer package is required.
- Is there a Laravel port, fork or shim of liip/search-bundle?
- No. There is no laravel-liip-search shim, no maintained fork and no notable gist, and the package has zero dependents whose patches you could borrow. You would be reimplementing the idea from scratch rather than integrating existing code.
- Can I use Zend Lucene directly in a Laravel app instead?
- Zend Lucene is a standalone PHP library that writes an index to disk, so it is not framework-coupled and could technically be called from Laravel. In practice it is effectively unmaintained, has no real concurrency story for multi-server deployments, and offers none of the relevance tooling of modern engines. Use Scout with Meilisearch or Typesense unless you have a hard constraint.
Weaver
How can I help you explore Laravel packages today?