PHPackages                             dwietor/cms-form-builder - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility &amp; Helpers](/categories/utility)
4. /
5. dwietor/cms-form-builder

ActiveLibrary[Utility &amp; Helpers](/categories/utility)

dwietor/cms-form-builder
========================

DWietor - CMS Form Builder for OroCommerce to easily create forms via UI

01PHP

Since May 1Pushed 6y ago1 watchersCompare

[ Source](https://github.com/dwietor/form-builder)[ Packagist](https://packagist.org/packages/dwietor/cms-form-builder)[ RSS](/packages/dwietor-cms-form-builder/feed)WikiDiscussions master Synced 3d ago

READMEChangelogDependenciesVersions (1)Used By (0)

DWietor - Cms Form Builder
==========================

[](#dwietor---cms-form-builder)

CMS Form Builder is a flexible OroCommerce extension that allows you to easily create forms via UI.

No longer need to have a dev team in order to add a form to your storefront. With this extension you can create forms in minutes without writing even a single line of code.

Installation
------------

[](#installation)

The easiest way to install CMS Form Builder is by using [Composer](https://getcomposer.org):

```
curl -sS https://getcomposer.org/installer | php
php composer.phar require dwietor/cms-form-builder
```

or if you have Composer already installed, just run:

```
composer require dwietor/cms-form-builder
```

After installation and running `oro:platform:update`, forms are accessible under Marketing &gt; Cms Forms in the back-office menu. Read more on [how you can create your first form.](./src/DWietor/Bundle/CmsFormBundle/Resources/doc/user_doc.md#how-to-create-your-first-form)

Features
--------

[](#features)

- Easily embed your forms in landing pages.
- Email notifications sent on every form response.
    - Possibility to set different custom email templates per email.
- Export form responses to CSV.
- Possibility to add additional CSS to form fields directly from UI.
- Many field types supported out of the box, like Email (with validation support) or Hidden field. [Full list](./src/DWietor/Bundle/CmsFormBundle/Resources/doc/field_types.md).
    - Especially useful when creating special forms for marketing campaign which gives you possibility to embed custom values (like campaign code) without exposing that to end users
- Seamless integration with ORO Reports engine. Powerful tool for creating custom reports based on form responses.

### Features for developers

[](#features-for-developers)

> Flexibility Driven Development

- Easy custom validation rules setup via YAML or events. [More info](./src/DWietor/Bundle/CmsFormBundle/Resources/doc/dev_doc.md#validation).
    - E.g. check if a given email already exists in a system or validate product SKU from Request for Quote form
- Easily create your own form field types with custom type-specific options and/or custom validation. [Have a look at the example.](./src/DWietor/Bundle/CmsFormBundle/Resources/doc/dev_doc.md#how-to-add-new-field-type)
- Most of the functionality is covered either with interfaces, events or DI tags which gives you a possibility to inject your code on every single stage of the process.

Documentation
-------------

[](#documentation)

- [For developers](./src/DWietor/Bundle/CmsFormBundle/Resources/doc/dev_doc.md)
- [For users](./src/DWietor/Bundle/CmsFormBundle/Resources/doc/user_doc.md)

License
-------

[](#license)

[OSL-3.0](./LICENSE) Copyright (c) 2019 David Wietor

###  Health Score

17

—

LowBetter than 6% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity1

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity34

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/60348891?v=4)[dwietor](/maintainers/dwietor)[@dwietor](https://github.com/dwietor)

---

Top Contributors

[![dwietor](https://avatars.githubusercontent.com/u/60348891?v=4)](https://github.com/dwietor "dwietor (5 commits)")

### Embed Badge

![Health badge](/badges/dwietor-cms-form-builder/health.svg)

```
[![Health](https://phpackages.com/badges/dwietor-cms-form-builder/health.svg)](https://phpackages.com/packages/dwietor-cms-form-builder)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
