Weave Code
Form Bundle Laravel Package
netvlies/form-bundle
Netvlies FormBundle extends Symfony's form component with reusable form types, extensions and helpers, making it easier to build, customize and render complex forms in PHP applications.
NetvliesFormBundle
Frequently asked questions about Form Bundle
- Is netvlies/form-bundle a Laravel package?
- No. Despite appearing in Laravel-oriented package catalogs, netvlies/form-bundle is a Symfony 2 bundle that assumes Symfony bundle registration via AppKernel, the Symfony service container and event dispatcher, Twig, Sonata Admin, and Doctrine ORM. It has no Laravel service provider, facade, config publishing, or Eloquent integration. Treat the Laravel framing as a catalog artifact, not a supported use case.
- Can I install netvlies/form-bundle in a Laravel application with Composer?
- Composer may resolve the package, but nothing will work without a Symfony 2 kernel, Sonata Admin, and Doctrine wiring. There is no adapter path that preserves the bundle's value inside Laravel, and the cost of writing one exceeds a native rebuild. Use the package as a requirements reference and implement the capability directly on Laravel.
- Which Symfony, PHP, Sonata Admin, and Doctrine versions does netvlies/form-bundle require?
- The bundle targets the Symfony 2 era, typically 2.7 or 2.8, alongside Sonata Admin and Doctrine ORM, with Twig for rendering. The exact pins live in its composer.json, and the transitive dependencies are the real constraint. None of those branches are under active security support today, so check every pinned version against current end-of-life dates before considering it.
- Does netvlies/form-bundle work with Symfony 5, 6, or 7?
- No. The code is written against Symfony 2 idioms, older bundle and service container conventions, and stale transitive dependencies, so adopting it on modern Symfony collides with the framework rather than integrating with it. The only defensible hosting environment is an existing Symfony 2.7 or 2.8 installation with Sonata Admin and a bounded remaining lifespan. Even there you would be maintaining a fork, not consuming a dependency.
- Is netvlies/form-bundle still maintained?
- Effectively no. The project has roughly 13 stars, zero dependents, no inherited community, and no clearly named upstream owner, which means no maintenance, no security-response channel, and no CI or advisories you can inherit. If you use it at all, the fork is yours to own, patch, and audit. Identify an internal owner before any code is written.
- What does netvlies/form-bundle actually do for forms and submissions?
- It lets administrators define forms through Sonata Admin, compiles stored field definitions into a Symfony form at runtime, stores submissions, sends mail on submit, and provides tabular exports. The underlying model is flat and monolithic: a form has fields, and submissions are stored against those fields. Advanced behavior such as conditional branching, partial saves, per-field permissions, multilingual labels, or API-first submission is not documented and must be verified in the code.
- How do notifications and exports work in netvlies/form-bundle?
- The bundle mails results on submission and offers tabular export of stored submissions, but the details are undocumented. Mail retry behavior, templating, logging, and failure visibility are unclear, and export formats, streaming versus in-memory processing, and row limits are not specified. Expect to reverse-engineer these from the Admin, Entity, and controller code before relying on them in production.
- How do I rebuild netvlies/form-bundle functionality in Laravel?
- Map each capability onto a first-class Laravel equivalent: form schema and validation via Laravel's validator or form requests, an admin panel such as Filament or Nova for defining forms, Eloquent migrations for storing submissions, queued jobs and mailables for notifications, and maatwebsite/excel or streamed CSV for exports. This native rebuild is the recommended integration approach, and it uses the bundle only to inform the requirement set. Design the submission schema and notification semantics deliberately rather than inheriting them.
- Are there security concerns with netvlies/form-bundle?
- Yes, and they are non-trivial because the bundle both stores user submissions and sends mail. There is no clear test coverage, no security-response channel, and no CVE visibility into the transitive dependencies. Decide up front whether the intended use is trusted internal forms or public-facing submission, since that determines whether the attack surface is acceptable at all.
- What should I use instead of netvlies/form-bundle?
- On Laravel, build it natively with Filament or Nova for the admin side, Laravel validation and Eloquent for schema and persistence, queued mailables for notifications, and maatwebsite/excel for export. On modern Symfony, use the current Form component with maintained admin tooling. Either way, log the bundle as a scoped spike input rather than a platform dependency, and translate its form, field, submission, notification, and export decomposition into acceptance criteria on the real stack.
Weaver
How can I help you explore Laravel packages today?