netvlies/form-bundle

NetvliesFormBundle

Netvlies FormBundle

, _(*1)

The Netvlies FormBundle enables users to create basic forms through the Sonata Admin Bundle. It includes form configuration, storage of results, sending of notifications when a form is filled in and even the possibility to export form results through the Sonata list view., _(*2)

, _(*3)

Forms created using the FormBundle can be retrieved using the form service or be directly shown by using the show_form function provided by the FormBundle Twig extension., _(*4)

, _(*5)

Requirements

• Symfony
• Dependencies:
  • PHPExcel

Installation

Install the bundle

``` bash $ curl -s http://getcomposer.org/installer | php $ php composer.phar require netvlies/form-bundle, <sub>(*6)</sub>

Composer will install the bundle to your project's `vendor/netvlies` directory.

### Enable the bundle via the kernel

``` php
<?php
// app/AppKernel.php

public function registerBundles()
{
    $bundles = array(
        // ...
        new Netvlies\Bundle\NetvliesFormBundle\NetvliesFormBundle(),
        new Gregwar\CaptchaBundle\GregwarCaptchaBundle(),
    );
}

Configuration

By default the bundle uses default Symfony form rendering and provides configuration to customize the templates used., <sub>(*7)</sub>

netvlies_form:
    templates:
        form: MyBundle:Form:form.html.twig
        fields: MyBundle:Form:fields.html.twig

Read the documentation on form customization for more information on tweaking the form layout for your project., <sub>(*8)</sub>

Routing

This bundle requires no specific routing configuration., <sub>(*9)</sub>

Usage

After installation and configuration, the service can be directly referenced from within your controllers., <sub>(*10)</sub>

<?php
public function indexAction($formId)
{
    $form = $this->get('netvlies.form')->get($formId);

    ...
}

Or directly from the view., <sub>(*11)</sub>

{{ show_form(formId) }}

Form submit and success handling

The bundle provides a default success listener which handles default functionality like storing a result and sending a confirmation email (when enabled through the admin). Of course you can implement your own application specific success handling by overriding the default listener (netvlies.listener.form.success) or attaching an additional listener. Whichever option you prefer. The same holds for the submit listener, which handles the form posts., <sub>(*12)</sub>

Attaching an additional listener

``` yml // app/config/services.yml, <sub>(*13)</sub>

acme.listener.form.success: class: Acme\DemoBundle\EventListener\FormSuccessListener calls: - [ setContainer, [@service_container] ] tags: - { name: kernel.event_listener, event: form.success }, <sub>(*14)</sub>

### Overriding the default listener

``` yml
// app/config/services.yml

netvlies.listener.form.success:
    class: Acme\DemoBundle\EventListener\FormSuccessListener
    calls:
      - [ setContainer, [@service_container] ]
    tags:
      - { name: kernel.event_listener, event: form.success }

Translations

The bundle makes use of the Symfony validation messages and provides translation files for bundle specific captions. All of these translations can be overridden by creating your own translation files and putting them in one of the directories specified in the translations documentation., <sub>(*15)</sub>

For instance, to customize the messages for your application, you could create the following translations file., <sub>(*16)</sub>

``` yml // app/Resources/translations/validators.nl.yml, <sub>(*17)</sub>

This value should not be blank.: Dit veld mag niet leeg zijn. This value is not a valid email address.: Dit is geen geldig e-mailadres. ```, <sub>(*18)</sub>

Contribute

You can contribute to this bundle by issuing a pull request. The following are improvements we would like to see implemented somewhere in the near future., <sub>(*19)</sub>

• File upload field
• Easy injection / registration of custom field types
• Functional tests

Please note that the goal of this bundle is enabling the end user to easily create basic forms and not to create a complex one-bundle-fits-all solution that handles all possible types of forms. So please keep it simple., <sub>(*20)</sub>