Form Extension

In this document we will be explaining the actual state of our forms and their extensions. Right now, solution of extending forms is not complete and there will be several tasks that will assure better extending.

At this time we do not have every single form in our application ready for extension, the list of not prepared forms for extensions is below:

  • ProductMassActionFormType
  • VariantFormType
  • OrderItemFormType
  • OrderPaymentFormType
  • OrderTransportFormType

If you want to see example of extending one of these forms please check this link.

What can we use for creating our own forms

We created some form types which can help you with creating your own form types. You can find them in separate article

Adding fields into already existing form types in administration

Imagine that you have added new property into Product entity and you want this property to be set in administration using forms.

For this cases you can use FormExtensions in namespace App/Form/Admin that extends Symfony\Component\Form\AbstractTypeExtension, which has function called getExtendedType(). Implement this function and return class of ProductFormType and add your fields into form. If you create new extension you need to register it in config/forms.yaml

Changing rendering of already existing form type

If you want to change way the form is rendered or if you want to add your own classes you need to follow few steps. Many of our forms have their own theme which describe on how to render form row. These files are located in Shopsys/FrameworkBundle/Resources/views/Admin/Form folder. Copy theme of form type you want to change into your project namespace and replace file you want to change with your own file in twig/form_themes in config/packages/twig.yaml file. Now you can change whatever you want.

Remember that files that you copy into your project cannot be automatically upgraded with newer versions of Shopsys Platform.

If you want to change the whole style of rendering forms in administration you need to copy whole theme.html.twig which defines the style of rendering default symfony rows. You can read more about theme.html.twig below.

Adding your own form type

You can add your own form type if you want. Just create your own FormType, for example MyAmazingFormType, if you want to influence how this form type will be displayed you need to create theme for this form type.

Create new file into templates/Front/Form directory, name it for example myAmazingFields.html.twig and register this theme into twig/form_themes in config/packages/twig.yaml.

Now you can define how form type will be rendered. There are two options with which you can influence rendering of form type.


Form row is used for rendering whole row, including the label of form, your icons etc. form_row should call form_widget, form_errors and form_label.


Form widget defines rendering of actual input.

Just remember that you need to let Symfony know which form type you are defining. If you want to define rendering of MyAmazingFormType your form_widget and form_row should be named my_amazing_widget and my_amazing_row.


This template is used for custom rendering of forms and form fields and it extends form_div_layout.html.twig from Symfony. There are two theme.html.twig files as one is used for administration and the other for front-end. It contains definition of blocks that are used for rendering forms

  • form_start - renders the start tag of the form
  • form_end - renders the end tag of the form
  • form_row - renders the label, any errors, and the HTML form widget for the given field
    • form_widget - renders HTML form widget for the given field
    • form_errors - renders block with list of validation errors for the given field
    • form_label - renders label for the given field including red asterisk if the field is required

and blocks of custom form widgets for various FormTypes eg.:

Changing order of groups and fields

All form types contain option called position. With this option you can specify position of your group or field on the same hierarchical layer.

Option position can contain four different values:

    ->add('g', TextType::class, ['position' => 'last'])
    ->add('a', TextType::class, ['position' => 'first'])
    ->add('c', TextType::class)
    ->add('f', TextType::class)
    ->add('e', TextType::class, ['position' => ['before' => 'f']])
    ->add('d', TextType::class, ['position' => ['after' => 'c']])
    ->add('b', TextType::class, ['position' => 'first']);

The output will be: A => B => C => D => E => F => G.


More examples can be found here.

Changing order of existing groups and fields

Implementation of FormBuilderInterface contains method setPosition that can change order of existing field.

$builder->get('c')->setPosition(['after' => 'b']);


Because FormBuilderInterface doesn't declare method setPosition, your IDE will warn you that method doesn't exist.