Weave Code
Form Bundle Laravel Package
kunstmaan/form-bundle
KunstmaanFormBundle adds configurable form building and submission handling to Symfony applications, with admin integration for the Kunstmaan CMS. Create forms, manage fields, store submissions, and process results through the familiar Kunstmaan bundle workflow.
KunstmaanFormBundle brings configurable, editor-managed forms to Symfony applications built on the Kunstmaan CMS. It lets administrators create forms in the backend, define fields and validation, and publish them on site pages, while submitted data is captured and managed through the same admin environment.
- Admin-driven form creation and editing
- Dynamic fields with validation
- Stored form submissions for review
- Symfony Form and Kunstmaan CMS integration
- Reusable form pages for content editors
Frequently asked questions about Form Bundle
- Can I install kunstmaan/form-bundle in a Laravel application?
- No. This is a Symfony bundle that registers through the Symfony kernel and ships service container definitions, Doctrine ORM entities, Twig templates, and a hard dependency on KunstmaanPagePartBundle, which pulls in the wider Kunstmaan CMS bundle set. Laravel has no bundle or kernel registration concept, and service providers, Eloquent, and Blade are not drop-in substitutes for what this package expects. A Composer require against a modern Laravel app will almost certainly fail dependency resolution.
- What is KunstmaanFormBundle used for?
- It is the form builder for the Kunstmaan CMS. Editors assemble flexible forms with a drag-and-drop interface and customizable fields, attach them to pages as page parts, then capture and review submissions and configure confirmation emails, storage, exports, and notifications. It is a CMS admin feature rather than a standalone form library.
- Is kunstmaan/form-bundle still maintained?
- Effectively no. The last release was 2014-07-18, the repository has around 19 stars and zero dependents, and there has been no maintainer activity for roughly a decade. Treat unpatched CVEs in transitive dependencies, missing PHP 8 support, and the absence of trustworthy CI as expected rather than hypothetical.
- Which PHP, Symfony and Laravel versions does kunstmaan/form-bundle support?
- The 2014 release line targets PHP 5.3-5.6 era constraints, Symfony 2.x components, Doctrine 2.x, and Twig 1.x. It is not compatible with PHP 8+, Symfony 5, 6, or 7, Doctrine 3.x, or Twig 2/3, and it supports no Laravel version at all. Any environment running it is by definition end-of-life.
- How do I install and register KunstmaanFormBundle?
- Realistically it only installs inside a Symfony 2.x application that already runs KunstmaanPagePartBundle and the broader Kunstmaan CMS bundle set, where you register it in the Symfony kernel and let its container definitions and Doctrine mappings load. There is no supported installation path on Laravel or on modern Symfony. If you are evaluating it, spin up an isolated Symfony 2.x container first to confirm the feature set actually matches your requirements.
- Can I bridge kunstmaan/form-bundle into Laravel using Symfony component shims?
- I would explicitly recommend against it. The runtime contract expects Symfony's HttpKernel, event dispatcher, and Doctrine entity manager, none of which coexist cleanly with Laravel's request lifecycle and Eloquent. The bridging effort exceeds building a form builder on Laravel's native stack by an order of magnitude, and the result would still inherit an abandoned dependency graph.
- What are the best Laravel alternatives to KunstmaanFormBundle?
- Migrate the requirements, not the code. On the Laravel side, evaluate Filament, Statamic, or a dedicated form package, or build on native validation, Eloquent, and Blade with Livewire for dynamic fields. On the Symfony side, Symfony Forms combined with EasyAdmin covers the same ground with active maintenance.
- How does KunstmaanFormBundle store and export form submissions?
- Submissions are persisted as Doctrine ORM entities, which editors review in the CMS admin and can export, with configurable confirmation emails and notifications layered on top. Because the bundle is unmaintained, that submission store receives no security patches. Check GDPR and data residency obligations before putting any regulated data into it.
- How do I migrate away from KunstmaanFormBundle?
- Use this repository as a reference implementation for the data model, which is essentially form definition to field definitions to submission records, and rebuild on native primitives. For a legacy Symfony estate, pin the existing version, freeze upgrades, isolate the bundle behind an internal interface, and schedule replacement. Do not attempt to carry it forward across Symfony majors, because the PagePart coupling makes that a CMS migration rather than a bundle upgrade.
- What production risks come with this bundle, and are there GDPR concerns?
- Technical risk is high and concentrated in abandonment: no PHP 8 compatibility, no PSR-4/PSR-12 guarantees, no CI you can trust, and unpatched transitive dependencies with no downstream consumers validating compatibility. The low package score and opportunity score reflect that this is a legacy artifact, not an emerging capability. If you handle personal data, an unmaintained submission store is a compliance liability, so quantify replacement scope before going further.
Weaver
How can I help you explore Laravel packages today?