- Can I install akyos/form-bundle in a Laravel application instead of Symfony?
- Not natively. FormBundle is a Symfony bundle built on Symfony's Bundle architecture, DependencyInjection and HTTP Foundation ParameterBag semantics, and the README declares Symfony ^8.0 as a hard requirement. Laravel 11 and 12 currently pin symfony/* components to ^7.0, so Composer will likely block installation without --ignore-platform-reqs or a constraint override, and even then the bundle's service providers and Twig rendering will not run in Laravel. Realistic integration options are an API microservice, a hybrid Symfony sub-app, or extracting the feature into Laravel-native packages.
- What does akyos/form-bundle actually do and what are its dependencies?
- It provides configurable contact forms in the style of WordPress's Contact Form 7: dynamic field definitions, stored submissions, export, and Twig-based rendering. It is part of the AkyosCMS stack for Symfony and requires akyos/core-bundle ^8.0 and akyos/cms-bundle ^8.0 alongside the framework itself. Form definitions are declarative rather than Eloquent or FormRequest driven.
- What PHP and Symfony versions does FormBundle 8.0 require?
- The package requires PHP 8.4 or newer and Symfony ^8.0, plus the Akyos CoreBundle and CmsBundle at ^8.0. That is a stricter platform baseline than most Laravel applications run today. Check the composer.json of the specific tag before any proof of concept.
- Is there a Laravel alternative to akyos/form-bundle?
- Yes, and several are mature. spatie/laravel-form-builder covers dynamic form definitions, spatie/laravel-recaptcha replaces the Symfony-only karser/recaptcha3-bundle, and laravel-notification-channels or standard Mailables handle submission notifications. Combining those with Eloquent models and Blade views reproduces most of FormBundle's feature set without cross-framework friction.
- Why does FormBundle 8.0.3 use $request->query->get() and does that matter for Laravel?
- Symfony 8 removed the Request::get() method, so the 8.0.3 patch was needed. The maintainers switched to query/request ParameterBag access ($request->query->get(), $request->request->get()), which is exactly how the bundle reads parameters when editing builder components in the admin UI. Laravel's Request wraps the Symfony request but exposes input() and query() rather than encouraging direct ParameterBag calls, and the admin flow itself is Symfony forms code. This deepens the Symfony coupling rather than adding any Laravel affordance.
- Does akyos/form-bundle support reCAPTCHA v3?
- Yes, through the karser/recaptcha3-bundle dependency, which is Symfony-only and unchanged in the 8.0.x line. In a Laravel context you would swap it for spatie/laravel-recaptcha and re-implement the validation hook yourself. There is no built-in Laravel validation rule shipped by FormBundle.
- How do I install and configure akyos/form-bundle in a Symfony project?
- Run composer require akyos/form-bundle:^8.0 on PHP 8.4+ with Symfony 8, then register the bundle along with CoreBundle and CmsBundle. Forms are configured declaratively and rendered in Twig, with submissions and exports handled by the bundle. Verify the exact bundle registration and configuration keys against the repository README, since documentation is sparse.
- Can I store FormBundle submissions in an Eloquent model or send them through a Laravel Mailable?
- No. The package ships no Eloquent, FormRequest, Blade or Mailable integration, and the 8.0.3 release surfaces nothing along those lines. Submissions are persisted through the bundle's own Symfony-side mechanism and rendered via Twig. Any Laravel-side persistence would require a custom adapter or an API boundary between the two applications.
- Can I render FormBundle forms with Blade instead of Twig?
- Not directly. Rendering is Twig-based and tied to the Symfony templating layer, so Blade would require reimplementing the view layer and the field rendering helpers. If Blade output is a hard requirement, a Laravel-native form builder is the shorter path.
- Is akyos/form-bundle actively maintained and safe to depend on long term?
- The 8.0.3 patch shows an active maintainer tracking Symfony major releases, which is a positive signal within the Symfony ecosystem. However, it also confirms the package accelerates its divergence from Laravel's pinned Symfony 7.x components. Before adopting, confirm whether the constraint is ^8.0 only or ^7.0 || ^8.0, and plan for a patch on each future Symfony major upgrade.