Form the documentation:
If you wish, you can specify custom templates on a per Admin mapping basis. Internally, the CRUDController fetches this information from the Admin class instance, so you can specify the templates to use in the Admin service definition:
XML:
<service id="sonata.admin.post" class="Acme\DemoBundle\Admin\PostAdmin"> <tag name="sonata.admin" manager_type="orm" group="Content" label="Post"/> <argument /> <argument>Acme\DemoBundle\Entity\Post</argument> <argument /> <call method="setTemplate"> <argument>edit</argument> <argument>AcmeDemoBundle:PostAdmin:edit.html.twig</argument> </call> </service>
Yaml:
services: sonata.admin.post: class: Acme\DemoBundle\Admin\PostAdmin tags: - { name: sonata.admin, manager_type: orm, group: "Content", label: "Post" } arguments: - ~ - Acme\DemoBundle\Entity\Post - ~ calls: - [ setTemplate, [edit, AcmeDemoBundle:PostAdmin:edit.html.twig]]
An example of using setTemplates
:
XML:
<service id="sonata.admin.post" class="Acme\DemoBundle\Admin\PostAdmin">
<!-- ... -->
<call method="setTemplates">
<argument type="collection">
<argument key="edit">
AcmeDemoBundle:PostAdmin:edit.html.twig
</argument>
<argument key="list">
AcmeDemoBundle:PostAdmin:list.html.twig
</argument>
</argument>
</call>
</service>
Yaml:
services:
sonata.admin.post:
# ...
calls:
- [setTemplates, [{edit: AcmeDemoBundle:PostAdmin:edit.html.twig, list: AcmeDemoBundle:PostAdmin:list.html.twig }]]