- Is padam87/search-bundle compatible with Laravel?
- No. padam87/search-bundle is a Symfony2 bundle built on Symfony's DependencyInjection container, bundle registration, and Doctrine metadata. Laravel uses service providers, Eloquent, and a different container model, so there is no direct integration path. Composer requiring it into a Laravel app will likely produce autoload and container failures.
- Can I install padam87/search-bundle in a Laravel 10 or 11 app?
- You should not. It targets Symfony 2.x and PHP 5.x-era tooling and last shipped in 2014, while Laravel 10/11 requires PHP 8.1+ and modern PSR autoloading. There is no maintained bridge, so installation is not supported. Port the search concept natively or choose a Laravel-native package.
- What does padam87/search-bundle do?
- It adds configurable search to Symfony applications by defining searchable fields and filters, building queries from request parameters, and paginating results through Doctrine ORM. It was designed for Symfony2 controllers and repositories. It is not a Laravel package and is marked deprecated.
- Why is padam87/search-bundle deprecated?
- The repository is abandoned, with a last release in April 2014, very few stars and dependents, and no security or compatibility updates. It depends on end-of-life Symfony 2.x and PHP 5.x conventions. Running it in a modern production stack is a compliance and maintenance risk.
- What Laravel packages should I use instead for search?
- For Laravel, evaluate Laravel Scout with Meilisearch or Algolia, Elasticsearch clients, or TNTSearch depending on whether you need full-text search, faceted filtering, or simple entity indexing. These are maintained and integrate with Eloquent and Artisan. Use the Padam87 bundle only as a design reference.
- Does padam87/search-bundle support PHP 8 and Symfony 6 or 7?
- No. The bundle was built for Symfony 2.x and PHP 5.x-era tooling, before widespread PSR-4 autoloading and modern typing. It does not support PHP 8.1+ or Symfony 6/7, and there is no maintained bridge. Modern Laravel versions are not compatible.
- How do I migrate from padam87/search-bundle to Laravel Scout?
- Treat the old bundle as a specification rather than a dependency. Extract the search abstraction, indexing lifecycle, and adapter contracts, then reimplement them behind a Laravel SearchDriver contract bound in a service provider. Drive indexing with Artisan commands and queued jobs, and if a Symfony service still depends on it, use a strangler pattern with dual writes and shadow reads before cutover.
- Can I use padam87/search-bundle with Doctrine ORM in Laravel?
- Doctrine ORM exists in Laravel via community packages, but this bundle still expects Symfony's container, bundle configuration, and metadata drivers. Those bootstrapping assumptions do not map to Laravel's service-provider model. A Doctrine-only port would effectively discard the bundle packaging and is not a practical integration.
- Is padam87/search-bundle maintained or secure for production?
- No. It is deprecated, unmaintained, and tied to end-of-life Symfony 2.x, so it receives no security patches or compatibility fixes. Production use would likely fail security and audit reviews. Choose a maintained search package or build a small native Laravel implementation.
- How does padam87/search-bundle handle filters and pagination?
- In Symfony, it defined searchable fields and filters, built Doctrine queries from request parameters, and paginated results. That behavior is easy to reproduce in Laravel with query scopes, request validation, and pagination. The value is the pattern, not the legacy code.