- Is folliked/form-bundle compatible with Laravel?
- No. It is a Symfony bundle built on the Symfony Form component and Twig rendering pipeline, and Laravel has no Symfony Forms runtime. Adopting it in Laravel means standing up Symfony Forms as a parallel abstraction or forking and rewriting the widgets, so it is not a clean architectural fit.
- Can I install folliked/form-bundle with Composer in a Laravel app?
- You can require the Composer package, but it expects Symfony bundle registration, a Symfony service container, and Twig form themes. Those expectations do not match Laravel's service container or Blade rendering. For a Laravel application, do not install it as a dependency.
- What Laravel versions does folliked/form-bundle support?
- It does not officially support any Laravel version. The package is a Symfony bundle from the Symfony 2–3 era, and its single release line ended on 2020-06-04. Expect PHP 5.6 or 7.x-era constraints and Symfony components rather than Laravel 8+ compatibility.
- Does folliked/form-bundle provide validation for Laravel forms?
- No. Its validation and error handling are tied to the Symfony Form component, not Laravel's validator. In a Laravel app you would need to rewrite the rules and error handling against Laravel validation. The package's built-in validation is useful only inside a Symfony Forms runtime.
- How do I render folliked/form-bundle forms in Blade?
- You cannot render them directly in Blade. The bundle relies on Twig form themes and Symfony's rendering pipeline for consistent output. Using it in Laravel would require porting templates or running Twig alongside Blade, which adds complexity rather than reducing boilerplate.
- Is folliked/form-bundle maintained or safe for production?
- It is not maintained in any practical sense: zero stars, zero dependents, a single release line ending in 2020, and no community or security response path. Its vendored jQuery plugins, old TinyMCE and Recaptcha clients, and GD image captcha carry known risk classes. Treat it as reference code for widget ideas, not as a production dependency.
- What are the best alternatives to folliked/form-bundle for Laravel forms?
- Use Laravel's Blade views and validator as the baseline, then choose maintained per-widget packages where needed. Common replacements include hCaptcha, Turnstile or a maintained Laravel captcha validator, TinyMCE via npm or CDN, flatpickr or native date inputs, Select2 for autocomplete, noUiSlider for sliders, FilePond or Dropzone for uploads, and intervention/image for image handling.
- Why does folliked/form-bundle use jQuery plugins and a GD image captcha?
- The bundle reflects the jQuery and Symfony 2–3 era in which it was written. Its widgets are jQuery plugins, and its captcha is a server-side GD-rendered image tied to session state. Modern OCR and bot farms solve that kind of captcha easily, and rendering it adds CPU and session-store load per request.
- Can I reuse folliked/form-bundle's TinyMCE, Recaptcha or captcha widgets in Laravel?
- Not directly. They are Symfony form types rendered through Twig themes, so they do not plug into Blade or Laravel's validation flow. You could extract the markup and JavaScript patterns as reference, but you should reimplement each widget against a maintained package such as TinyMCE, hCaptcha, Turnstile or a Laravel recaptcha validator.
- How should I test or migrate away from folliked/form-bundle?
- Do not sequence it as a first-wave dependency. If the functionality is genuinely needed, run a short spike to extract widget markup and JavaScript patterns, then reimplement them in Blade with maintained packages. If your organization is actually on Symfony, pin it in a sandbox, run composer audit, test behind a feature flag, and only then decide whether to fork or replace it.