Since the placeholder shouldn't be used as placeholder, rename the field Placeholder to Example. It should be used as example field under the form-field like:

Label
Input
Example

Don't miss to add a documentation for the usage if the field should have a placeholder (use the title field as placeholder-item - in case of the required attribute)

The dynamic list should also be searchable.

Instead of redirecting to a ?send=true it should be possible for the content manager to choose a internal link to redirect to.

Add a hide in email checkbox to avoid that specific fields are sent with email.

If i create a form field with checkboxes and set it as mandatory-field, nothing happens. The fields aren't declared as required.

Please remove the mandatory field marker from the checkboxes or set the attribute to every checkbox in checkboxes.

Add possibility to avoid form save based on events.

• getName is deprecated and should getBlockPrefix be used for the theming prefixes.

So we can use a short title in notification mail and the (sometimes) long text in the label of the checkbox.

If you use the form bundle with the community bundle it is nice to know the user ID of the user which filled the form.

As example I'm missing following default fields:

• Datetime
• Time

The form are loaded with the user locale instead of content locale so a permission denied error appears.

How to reproduce

1. have only a webspace with the locale en
2. login with a user which system locale is de
3. he can now not accessing the form section

The dynamic form email configuration should show the fallback mail addresses as placeholder.

Backend for CC and BCC mail receivers

• Move form fields to top
• Add new block with 2 Types (CC, BCC) and email and name field
• Create FormTranslationEmails entity
• FormManager handle save
• Configuration to activate this feature
• Configuration to set a mail template

    mail:
       cc: # canBeEnabled
       notify_template: "..."
       customer_template: "..."

Website

• DynamicFormType deactivate here the default mails
• MailSubscriber service ( listen to DynamicFormSaved event )
  • send Notify Emails with CC and BCC
  • send Customer Emails

So the to email address is set as replyTo when email address.

when you use a page multiple times for a form you should be able to archive old data.

That the developer dont need to create a form with all field type it would be a good feature to create a dummy form with all field type by command.

Currently only the formName is sent via the request all other data are read from the structure directly. https://github.com/alexander-schranz/sulu-form-bundle/blob/develop/Form/Builder.php#L81-L117

$id = FormId
$type = e.g. page, event, blog,
$typeId = e.g. pageUuid, blog id, event id
$typeName = e.g. pageTitel, blog titel
$locale = request.locale
$name = formName

To create the form only the formId, name and locale should be needed.
To save the form formId, locale, type, typeId should be needed.
For the media collection tree strategy also the typeName is needed to create a collection with the same name as the page.

The controller need to deactivate the requestAnalyzer to work correctly:

e.g.:

sulu_form.token:
    path: /form/token
    defaults: { _controller: SuluFormBundle:FormWebsite:token, _requestAnalyzer: false }

Also the ESI need to be called with _requestAnalyzer: false as attribute.

TODO:

• Update documentation render_esi
• Update website routing.yml

When not doing this the preview will not work correctly on pages with localization as folder.

Move from: alexander-schranz/sulu-form-bundle#78

Dynamic form types should be able to be added by a service.

TODO:

• Dynamic Type Pool
• Dynamic Type Interface
• CompilerPass
• Create exist types with as service

It should be possible that you can remove specific types by there names.

To have multiple submit buttons in the form add a new submit button type.

sulu feature tab per content type

On connection error with SMTP connection we doesn't get any errors in log files.

Solution:
https://github.com/sulu/SuluFormBundle/blob/develop/Mail/Helper.php#L123

$failed = null;
$return = $this->mailer->send($message, $failed);

$this->logger->error(var_export($failed));

return $return;

This need to create for exist media for forms new collection and move the media to the new collection.

This fix was included because the generated key are not set again after save.

https://github.com/alexander-schranz/sulu-form-bundle/blob/develop/Resources/public/js/components/forms/form/main.js#L205

The dropdown with all available types should be grouped.

e.g.:

• Text Types
  • Firstname
  • Lastname
  • ...
• Complex Types
  • Checkbox
  • Select
• Special Types
  • Attachment
  • Mailchimp
  • Recaptcha
• Additional Types
  • Headline
  • FreeText
  • Spacer

A placeholder should not be selectable.

https://symfony.com/doc/current/reference/forms/types/datetime.html

The notify email should have also the possibility of adding a text e.g. when the form creator is not the receiver of the email.

It should be possible configure what is are possible grid withs.

There should also be a tab of the list data on the form itself.

Add a form theme based on the form_div_layout.html.twig that it works without create a custom form theme.

The current handling of static form should be removed and implement static form like dynamic forms.

If you use the form bundle with the community bundle or other. It should be able to activate a autofill API. This should be a json api which autofill the form by an ajax request. JS need to be included by the user itself.

Only activatable by flag and need to configure which fields should be return because high risk of privacy!

It should possible to have a from and to date in the csv export to filter the data.

The https://github.com/alexander-schranz/sulu-form-bundle 1.0 release should be migrate able to 0.1 of this repo.

TODO

Table Names:

• l91_fo_dynamic -> fo_dynamics
• l91_fo_form -> fo_forms
• l91_fo_form_translations -> l91_fo_form_translations
• l91_fo_form_fields -> fo_form_fields
• l91_fo_form_field_translations -> fo_form_field_translations

RENAME TABLE `l91_fo_dynamic` TO `fo_dynamics`;
RENAME TABLE `l91_fo_form` TO `fo_forms`;
RENAME TABLE `l91_fo_form_field_translations` TO `fo_form_field_translations`;
RENAME TABLE `l91_fo_form_fields` TO `fo_form_fields`;
RENAME TABLE `l91_fo_form_translations` TO `fo_form_translations`;

Other changes:

• CSRF Token include

It will be nice to integrate the form-select content-type into blocks.
Currently one single form in blocks will work but data will not be visible in the Formula-Tab.

The form should be split in 3 tabs

• Form
• Email
• Website

Line: 193

If I give the form_select property the name 'form' as proposed in https://github.com/sulu/SuluFormBundle/blob/master/Resources/doc/dynamic.md the styling in the admin area breaks (at least when I add it to a blocks content_type)

As you can see in this screenshot (the block 'Formulier'):

It's because of this css selector, which isn't specific enough:

Based on #32.
It should have 2 sections notify email and customer email also add an info text or change the name.

Here I describe the whole refractoring which is needed before the first release to avoid future bc breaks:

Structure

• Admin
  • FormAdmin.php
  • FormNavigationProvider.php
  • DynamicListNavigationProvider.php ( new )
  • StaticListNavigationProvider.php ( rename )
• Content
  • Types
    • FormSelect.php
• Controller
  • FormController.php
  • FormWebsiteController.php
  • StaticController.php ( renamed )
  • DynamicController.php ( new )
• DependencyInjection
  • CompilerPass
    • StaticListProviderCompilerPass.php ( rename )
    • DynamicListBuilderCompilerPass.php ( new )
    • DynamicFormFieldTypeCompilerPass.php ( new )
  • Configuration.php
  • SuluFormExtension.php
• Dynamic
  • FormBuilder.php ( new )
  • FormBuilderInterface.php ( new )
  • FormFieldTypePool.php ( new )
  • FormFieldTypeInterface.php ( new )
  • Types
    • ...
• Entity
  • Dynamic.php
  • Form.php
  • FormEmail.php ( new )
  • FormEmailTranslation.php ( new )
  • FormField.php
  • FormFieldTranslation.php
  • FormRepository.php ( moved )
  • FormTranslation.php
• Event
  • Listener
    • RequestListener.php ( moved )
  • Subscriber
    • MailSubscriber.php ( new )
    • MailchimpListSubscriber.php ( moved )
    • FormSubmitSubscriber ( new )
  • FormValidateEvent.php ( new )
  • FormSubmitEvent.php ( new )
  • FormSavedEvent.php ( renamed )
• Form
  • Type
    • AbstractType.php ( remove )
    • DynamicFormType ( refractor )
    • SuluMediaType ( new )
  • FormHandler.php ( refractor )
  • FormLoader.php ( new )
• ListBuilder
  • DynamicListBuilder.php ( new )
  • DynamicListBuilderInterface.php ( new )
  • DynamicListFactory.php ( new )
  • DynamicListFactoryInterface.php ( new )
  • StaticListBuilder.php ( renamed (moved provider) )
  • StaticListFactory.php ( renamed (moved provider) )
• Mail
  • SwiftMailerHelper.php ( renamed )
  • NullMailerHelper.php ( renamed )
  • MailerHelperInterface.php ( renamed )
• Manager
  • FormManager.php
• Media
  • CollectionStrategyInterface.php
  • CollectionTreeStrategy.php ( new default )
  • CollectionSingleStrategy.php
• Resources
  • ...

FormBuilder

Main part is the Form builder what is needed to create a dynamic form.

• Form ID
• Type
• TypeId
• TypeName
• Locale (optional)
• Name (optional default "form") (needed when have multiple forms)

Dynamic Entity

• uuid -> typeId
• new type (default is "page")
• new typeName (default is structure title)

Sketch

TODOs

Exist issues and PRs:

• #4 Dynamic Form Field Pool
• #17 Include Mail Subscriber
• #24 Split form from Structure

It's a issue in case of "bug" from symfony2 form theme.

If we have marked a select field (salutation) as mandatory field, symfony2 removes the required attribute from select (because no default option with empty value exist).
In this case the select field wouldn't be marked as required - only the label will be marked as required.

It isn't a important issue.