- Is kissifrot/select2entity-bundle a Laravel package?
- No. It is a Symfony2 bundle that extends Symfony's Form component (EntityType/FormTypeExtension), uses Twig for rendering, and queries Doctrine entities through the EntityManager. It has no service provider, facade, config publishing, or Blade views, so there is nothing for Laravel's request lifecycle to hook into. The transferable part is only the pattern: replacing a large select element with a Select2 widget backed by a JSON search endpoint.
- Can I install select2entity-bundle in a Laravel 10 or Laravel 11 application?
- Not realistically. Composer resolution fails because the bundle constrains Symfony 2.3–2.8 components, Twig 1.x, and PHP 5.x/7.0-era packages that conflict with illuminate/* dependencies. Forcing it in with --ignore-platform-reqs produces a bundle that no part of a Laravel application ever invokes. Treat integration feasibility as effectively zero and reimplement the feature instead.
- What does Select2EntityBundle actually do?
- It turns Symfony EntityType form fields into AJAX-powered Select2 inputs so users can search and pick related entities from large tables without loading every row. A bundled controller endpoint runs search queries against your Doctrine entities and returns formatted results, while selections resolve back to real entity objects on submit. It supports single and multiple selections, configurable search fields, and configurable result formatting.
- Which PHP and Symfony versions does select2entity-bundle support?
- The bundle targets the Symfony 2.3–2.8 era, Twig 1.x, and PHP roughly 5.5 through 7.0. Symfony 2.x reached end of life in 2018, and those PHP branches are long unsupported. That places it two major PHP versions and three Symfony majors behind anything you would run in a current Laravel or Symfony project.
- How do I build Select2 AJAX entity autocomplete in Laravel without this bundle?
- Create a controller action that accepts a search term, applies a query scope, and returns JSON shaped like {results: [{id, text}], pagination: {more: bool}} with a capped paginate() call. In Blade, render a reusable component that initializes Select2 v4 with that route as its ajax URL. Use route model binding and eager-load only the columns you display. This is typically a one-to-two-day build, and it gives you full control over authorization, rate limiting, and result formatting.
- Does the bundle support multiple selections and pre-selected values?
- Yes. The bundle handles both single and multiple selection modes and lets you configure which fields are searched and how results are formatted. In a Laravel replacement, plan for array-valued input, proper validation of selected IDs, and initializing Select2 with existing selections on edit forms. Those are the same concerns, but you implement them in Laravel rather than inheriting them from a Symfony form extension.
- Is select2entity-bundle safe to run in production?
- No. Symfony 2.x is unpatched, so adopting any part of it means running dependencies with known CVEs and no remediation path. The project also shows one star, zero dependents, a single maintainer, and no security disclosure process, which is textbook busfactor-one abandonment. If you need this UX, build a small Laravel-native endpoint and keep the Select2 client library, which is actively maintained.
- What are good Laravel alternatives for searchable entity dropdowns?
- Use a Livewire component with a searchable select, a Blade component backed by a small JSON endpoint and Select2 v4, or a native datalist for bounded lists under a few hundred options. For very large datasets, pair the endpoint with Laravel Scout or a indexed search driver. All of these avoid the Symfony2 dependency and fit Laravel 10/11 on PHP 8.2 or 8.3.
- Why does select2entity-bundle show a 2026 release date when Symfony 2 is end-of-life?
- That date is a metadata anomaly: a 2026-07-24 release against a framework end-of-lifed in 2018 is inconsistent and should be treated as unreliable. Verify the actual tag contents if it ever matters, but it does not change the adoption decision. Nothing about a re-tagged abandoned Symfony2 bundle makes it compatible with modern Laravel.
- How hard is it to migrate a Symfony2 app off Select2EntityBundle to Laravel?
- There is no migration path from the package itself because there is nothing to port; the work is a reimplementation. Preserve the same JSON contract your front-end JavaScript expects (results, pagination.more, id, text) on Laravel or Symfony 6/7, then retire the bundle once traffic moves. If your organization has no Symfony2 footprint, which is likely given zero dependents, treat this as a greenfield build rather than a migration.