Book Image

Mastering Symfony

Book Image

Mastering Symfony

Overview of this book

In this book, you will learn some lesser known aspects of development with Symfony, and you will see how to use Symfony as a framework to create reliable and effective applications. You might have developed some impressive PHP libraries in other projects, but what is the point when your library is tied to one particular project? With Symfony, you can turn your code into a service and reuse it in other projects. This book starts with Symfony concepts such as bundles, routing, twig, doctrine, and more, taking you through the request/response life cycle. You will then proceed to set up development, test, and deployment environments in AWS. Then you will create reliable projects using Behat and Mink, and design business logic, cover authentication, and authorization steps in a security checking process. You will be walked through concepts such as DependencyInjection, service containers, and services, and go through steps to create customized commands for Symfony's console. Finally, the book covers performance optimization and the use of Varnish and Memcached in our project, and you are treated with the creation of database agnostic bundles and best practices.
Table of Contents (17 chapters)
Mastering Symfony
Credits
About the Author
About the Reviewers
Index

Overriding templates


In order to override a template that ships with a third-party bundle (such as SonataUserBundle), we have to create a duplicate of it in the app/Resources folder and modify it here.

To see how it works, let's start with the login page. At the moment, it looks ugly and empty and covered with some unnecessary elements.

Copy a few folders from sonata-project to your app/Resources folder as follows:

$ mkdir app/Resources/SonataUserBundle
$ cp -r vendors/sonata-project/user-bundle/Resources/views/app/Resources/SonataUserBundle/

Now edit Security/base_login.html.twig as follows:

{# app/Resources/SonataUserBundle/views/Security/base_login.html.twig #}
{% extends '::mavaBase.html.twig' %}
{% block mavaBody %}
    {% block fos_user_content %}
          {# rest of the template #}
     {% endblock %}
{% endblock %}

Here, you can see the benefit of saving blocks in separate files. As it is extended from the mava_base template, no menu will be shown, which is what we want. Visit the login...