- Is prolix/form-bundle a Laravel package?
- No. It is a Symfony 2 bundle that registers through AppKernel and the Symfony DependencyInjection container, and it extends Symfony's Form and Twig extension points. The Laravel-focused description is misleading, because Laravel has no bundle lifecycle and no Symfony DI compiler passes. Treat the composer name as a fork of the abandoned GenemuFormBundle rather than a Laravel package.
- Can I install prolix/form-bundle in a Laravel application?
- No, and it will not run even if you force it in. Laravel uses Blade, FormRequest and a completely different validation layer, so there is no architectural seam where Symfony 2 form types could plug in. Composer resolution also fails on PHP 8 because the constraints target Symfony 2 and PHP 5.x components. Adding ignore-platform-reqs only converts a clean install failure into a runtime failure.
- What extra form types does prolix/form-bundle provide?
- The bundle adds Captcha GD, TinyMCE, ReCaptcha, JQueryDate, JQueryAutocomplete, JQuerySlider, JQueryFile and JQueryImage form types. Each one is a Symfony form type plus a matching Twig theme and jQuery-era front-end assets. They were built for Symfony 2.3 to 2.7 applications, not for Blade views or Livewire components.
- Which Laravel versions does this package support?
- None. There is no Laravel service provider, facade, config file or publishable migration in the repository. Any claim of Laravel support in the package blurb is a category error. Do not plan a Laravel upgrade path around this package.
- What PHP and Symfony versions are required?
- The dependency constraints target Symfony 2.x components and PHP 5.x-era APIs. Symfony 2 reached end of life in 2016, with 2.8 following in 2018, and PHP 5.x is unsupported. That means the package conflicts with every currently supported Symfony release, including 5.4, 6.x and 7.x, and with PHP 8.x runtimes.
- Is prolix/form-bundle still maintained?
- No. The upstream GenemuFormBundle stopped active development around the Symfony 2.3 to 2.7 era. This fork shows zero stars, zero dependents and a single republish in 2022, with no maintainer triage or security response. Assume no bug fixes, compatibility updates or security patches will ever be released.
- Is it safe to use prolix/form-bundle in production?
- There is no meaningful test suite or CI signal, so any patch you apply becomes unverified code in your supply chain. All transitive dependencies sit on end-of-life Symfony 2 and PHP 5 branches, which is a standing CVE exposure. Combined with the lack of an active maintainer, the technical risk is high and not really mitigable.
- What should I use in Laravel instead of the file and image upload types?
- Use intervention/image for cropping and resizing, spatie/laravel-medialibrary for attaching media to Eloquent models, or Filament FileUpload if you are building an admin panel. Laravel's own upload handling and validation rules cover the rest of the flow. None of these require a Symfony bundle or Twig themes.
- What are the Laravel replacements for the captcha and ReCaptcha form types?
- Use google/recaptcha for ReCaptcha verification, or spatie/laravel-honeypot for a lighter bot trap backed by Laravel validation rules. Both plug into FormRequest validation rather than a form type, which fits Laravel's workflow. The Captcha GD type is usually replaced by a honeypot field or a hosted captcha service.
- How do I replace the autocomplete, date picker and rich text form types?
- For autocomplete, use Livewire or laravel/scout with a typeahead front end. For date and time input, flatpickr or Filament's date widgets are the common Laravel choices. For rich text, TipTap or Editor.js paired with an HTML sanitizer replaces the bundled TinyMCE wrapper.