Documentation » Admin

9. The Show action »

« 7. The List View

8. Creating and Editing objects


This document is a stub representing a new work in progress. If you’re reading this you can help contribute, no matter what your experience level with Sonata is. Check out the issues on Github for more information about how to get involved.

This document will cover the Create and Edit actions. It will cover configuration of the fields and forms available in these views and any other relevant settings.

8.1. Basic configuration


TODO: * global (yml) options that affect the create and edit actions * a note about Routes and how disabling them disables the related action * using configureFormFields() to set which fields to display * options available when adding fields, inc custom templates * link to the field_types document for more details about specific field types

8.1.1. FormGroup options

When adding a form group to your edit/create form, you may specify some options for the group itself.

  • collapsed: unused at the moment
  • class: the class for your form group in the admin; by default, the value is set to col-md-12.
  • fields: the fields in your form group (you should NOT override this unless you know what you’re doing).
  • box_class: the class for your form group box in the admin; by default, the value is set to box box-primary.
  • description: to complete
  • translation_domain: to complete

To specify options, do as follows:

// src/AppBundle/Admin/PersonAdmin.php

class PersonAdmin extends AbstractAdmin
    // ...

    public function configureFormFields(FormMapper $formMapper)
            ->tab('General') // the tab call is optional
                ->with('Addresses', array(
                    'class'       => 'col-md-8',
                    'box_class'   => 'box box-solid box-danger',
                    'description' => 'Lorem ipsum',
                    // ...
                    // ...

Here is an example of what you can do with customizing the box_class on a group

Box Class

8.2. Embedding other Admins


TODO: * how to embed one Admin in another (1:1, 1:M, M:M) * how to access the right object(s) from the embedded Admin’s code

8.3. Customizing just one of the actions


TODO: * how to create settings/fields that appear on just one of the create/edit views * and any controller changes needed to manage them

Found a typo? Something is wrong in this documentation? Just fork and edit it!