Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Symfony2 Essentials
Symfony2 Essentials

Symfony2 Essentials:

Arrow left icon
Profile Icon Wojciech Bancer
Arrow right icon
$19.99 per month
Full star icon Full star icon Half star icon Empty star icon Empty star icon 2.7 (7 Ratings)
Paperback Sep 2015 158 pages 1st Edition
eBook
$22.99 $25.99
Paperback
$32.99
Subscription
Free Trial
Renews at $19.99p/m
Arrow left icon
Profile Icon Wojciech Bancer
Arrow right icon
$19.99 per month
Full star icon Full star icon Half star icon Empty star icon Empty star icon 2.7 (7 Ratings)
Paperback Sep 2015 158 pages 1st Edition
eBook
$22.99 $25.99
Paperback
$32.99
Subscription
Free Trial
Renews at $19.99p/m
eBook
$22.99 $25.99
Paperback
$32.99
Subscription
Free Trial
Renews at $19.99p/m

What do you get with a Packt Subscription?

Free for first 7 days. $19.99 p/m after that. Cancel any time!
Product feature icon Unlimited ad-free access to the largest independent learning library in tech. Access this title and thousands more!
Product feature icon 50+ new titles added per month, including many first-to-market concepts and exclusive early access to books as they are being written.
Product feature icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Product feature icon Thousands of reference materials covering every tech concept you need to stay up to date.
Subscribe now
View plans & pricing
Table of content icon View table of contents Preview book icon Preview Book

Symfony2 Essentials

Chapter 2. Your First Pages

Most modern PHP frameworks follow a classic MVC concept. Symfony2 is also an MVC framework, so we do have controllers, models, and views. In this chapter, we will learn about these building blocks to see how Symfony2 organizes things:

  • Review of the default bundle structure and recommendations
  • Setting up the first routings and controllers for the home screen
  • Working with templates
  • Creating the initial database schema and models
  • Loading sample fixtures
  • Looking into migration throughout the chapter

Everything is a bundle

In the previous chapter, we dug in to the basic Symfony2 directory structure. Within the src directory, we already had two bundles: one called DemoBundle within the Acme subdirectory and the other one within AppBundle.

DemoBundle is a showcase of an example bundle that has existed since the beginning of Symfony2. It has been created to demonstrate how Symfony2 organizes things. AppBundle is a relatively new thing, introduced in Symfony 2.6 with a new concept of work.

Until the 2.6 version, it was recommended to contain a bundle within the vendor namespace. With Symfony 2.6 and its new best practices rules, it is now recommended to keep the custom application code within the handy AppBundle and create other bundles only if you want to create reusable code to be shared among your other projects.

Bundles don't have a fixed directory structure. In fact, you can have a bundle without most of the directories. If you create a utility bundle, it will probably have only...

The configuration format

Symfony2 can handle configuration in different formats: YAML, XML, and annotations. The main configuration files within app/config are provided with the YAML format. XML is usually harder to read, and is used only with third-party bundles.

While both YAML and XML configuration are pretty straightforward and need no explanations, we should stop by annotations for a while. As an example, see the AppBundle/Controller/DefaultController class:

namespace AppBundle\Controller;

use Sensio\Bundle\FrameworkExtraBundle\Configuration\Route;
use Symfony\Bundle\FrameworkBundle\Controller\Controller;

class DefaultController extends Controller
{
    /**
     * @Route("/", name="homepage")
     */
    public function indexAction(Request $request)
    {
        // replace this example code with whatever you need
        return $this->render('default/index.html.twig', array(
            'base_dir' => realpath(
                $this-&gt...

Cleanups

Before we start writing our own app, we need to do some cleanups. We need to configure AppBundle to use the YAML configuration. While this is possible to switch the configuration format manually, we will remove the bundle (it doesn't contain much code yet), and we will generate a new bundle to demonstrate new bundle creation.

Recreating AppBundle

To recreate AppBundle, remove it first as follows:

$ rm -rf src/AppBundle

Remove it from app/AppKernel.php by removing the following line:

new AppBundle\AppBundle(),

Remove it's routing (app/config/routing.yml), which is as follows:

app:
    resource: @AppBundle/Controller/
    type:     annotation

Now we will need to generate it again. Issue the following command:

$ php app/console generate:bundle --namespace=AppBundle

Now provide the following answers to the generator:

Bundle name [AppBundle]: [Enter]
Target directory [.../todoapp/src]: [Enter]
Configuration format (yml, xml, php, or annotation): yml
Do you want to generate the whole...

Routing

Like with many other frameworks based on the concept of MVC, before any controller is actually executed, Symfony2 needs to know how to handle it. The Symfony routing configuration starts within the app/config/routing_*.yml file. Depending on which environment you fire up, this version of routing is fired up. Usually, this environment file loads the main app/config/routing.yml file, which loads other files from vendors, bundles, and so on. You can, of course, directly define your own single routings here, but it's usually recommended to keep the bundle-specific routings within the bundle itself, while using the main routing only to import resources.

As per the example provided earlier in this chapter, we know our app tries to import another resource file defined as @AppBundle/Resources/config/routing.yml. The @BundleName syntax is a shortcut to the bundle namespace (in our case AppBundle) but namespace can be longer if you include the vendor in your name. Let's take a look...

Templates – the View layer

Each MVC framework offers the View layer, and Symfony2 is no different. In Symfony1, we were using plain PHP code. Symfony has introduced a new templating engine named Twig. The Symfony syntax is more elegant — it's shorter and designed to be cleaner than regular PHP code in templates.

Note

We can still use it now. However, it's not the recommended approach, as in most cases, you will not find examples of a working bundle code in pure PHP.

Let's take a look at the template code within our bundle, src/AppBundle/Resources/views/Default/index.html.twig:

Hello {{ name }}!

Yes, this is it. As you can figure out, {{ name }} outputs the variable name. It is an equivalent of <?php echo $name; ?>. The code actually doesn't do much, and it is not a valid HTML code (it just outputs some text). Let's modify it a little:

{% extends '::base.html.twig' %}

{% block body %}
Hello {{ name }}!
{% endblock body %}

Now try to fire http...

Everything is a bundle


In the previous chapter, we dug in to the basic Symfony2 directory structure. Within the src directory, we already had two bundles: one called DemoBundle within the Acme subdirectory and the other one within AppBundle.

DemoBundle is a showcase of an example bundle that has existed since the beginning of Symfony2. It has been created to demonstrate how Symfony2 organizes things. AppBundle is a relatively new thing, introduced in Symfony 2.6 with a new concept of work.

Until the 2.6 version, it was recommended to contain a bundle within the vendor namespace. With Symfony 2.6 and its new best practices rules, it is now recommended to keep the custom application code within the handy AppBundle and create other bundles only if you want to create reusable code to be shared among your other projects.

Bundles don't have a fixed directory structure. In fact, you can have a bundle without most of the directories. If you create a utility bundle, it will probably have only some...

The configuration format


Symfony2 can handle configuration in different formats: YAML, XML, and annotations. The main configuration files within app/config are provided with the YAML format. XML is usually harder to read, and is used only with third-party bundles.

While both YAML and XML configuration are pretty straightforward and need no explanations, we should stop by annotations for a while. As an example, see the AppBundle/Controller/DefaultController class:

namespace AppBundle\Controller;

use Sensio\Bundle\FrameworkExtraBundle\Configuration\Route;
use Symfony\Bundle\FrameworkBundle\Controller\Controller;

class DefaultController extends Controller
{
    /**
     * @Route("/", name="homepage")
     */
    public function indexAction(Request $request)
    {
        // replace this example code with whatever you need
        return $this->render('default/index.html.twig', array(
            'base_dir' => realpath(
                $this->container
                     ->getParameter...

Cleanups


Before we start writing our own app, we need to do some cleanups. We need to configure AppBundle to use the YAML configuration. While this is possible to switch the configuration format manually, we will remove the bundle (it doesn't contain much code yet), and we will generate a new bundle to demonstrate new bundle creation.

Recreating AppBundle

To recreate AppBundle, remove it first as follows:

$ rm -rf src/AppBundle

Remove it from app/AppKernel.php by removing the following line:

new AppBundle\AppBundle(),

Remove it's routing (app/config/routing.yml), which is as follows:

app:
    resource: @AppBundle/Controller/
    type:     annotation

Now we will need to generate it again. Issue the following command:

$ php app/console generate:bundle --namespace=AppBundle

Now provide the following answers to the generator:

Bundle name [AppBundle]: [Enter]
Target directory [.../todoapp/src]: [Enter]
Configuration format (yml, xml, php, or annotation): yml
Do you want to generate the whole directory...

Routing


Like with many other frameworks based on the concept of MVC, before any controller is actually executed, Symfony2 needs to know how to handle it. The Symfony routing configuration starts within the app/config/routing_*.yml file. Depending on which environment you fire up, this version of routing is fired up. Usually, this environment file loads the main app/config/routing.yml file, which loads other files from vendors, bundles, and so on. You can, of course, directly define your own single routings here, but it's usually recommended to keep the bundle-specific routings within the bundle itself, while using the main routing only to import resources.

As per the example provided earlier in this chapter, we know our app tries to import another resource file defined as @AppBundle/Resources/config/routing.yml. The @BundleName syntax is a shortcut to the bundle namespace (in our case AppBundle) but namespace can be longer if you include the vendor in your name. Let's take a look at the bundle...

Left arrow icon Right arrow icon

Description

Symfony is a free and open source PHP MVC web application development framework, which helps you create and maintain web applications and replace recurrent coding tasks. It integrates with an independent library, PHPUnit, to give you a rich testing framework. It is one of the best and most popular frameworks available on the market. Popular projects such as Drupal, Laravel, and phpBB also use Symfony. Its well-organized structure, clean code, and good programming practices make web development a breeze. Symfony2 Essentials will guide you through the process of creating a sample web application with Symfony2. You will create a To-Do application, using a few of the most commonly used Symfony2 components, and discover how to perform these development tasks efficiently. This book introduces you to the Symfony framework with a quick installation guide and a brief explanation of its key features including the MVC architecture, twig templating, dependency injection, and more. You will learn to manage dependencies, create controllers, views, and API calls, and secure your application. Next, you will go through the steps that are common for most web applications, which include writing CRUD and AJAX, handling forms, validation, translations, and the command-line interface, and e-mail sending features. The book ends with best practices, debugging, profiling, and deployment procedures. By the end of this book, you will have learned how to combine a Symfony2 framework with other open source code to speed up the development process.

Who is this book for?

This book is aimed at experienced programmers, especially those familiar with a closely related technology such as Yii or Laravel, but who now want to learn Symfony quickly.

Product Details

Country selected
Publication date, Length, Edition, Language, ISBN-13
Publication date : Sep 08, 2015
Length: 158 pages
Edition : 1st
Language : English
ISBN-13 : 9781784398767
Languages :
Tools :

What do you get with a Packt Subscription?

Free for first 7 days. $19.99 p/m after that. Cancel any time!
Product feature icon Unlimited ad-free access to the largest independent learning library in tech. Access this title and thousands more!
Product feature icon 50+ new titles added per month, including many first-to-market concepts and exclusive early access to books as they are being written.
Product feature icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Product feature icon Thousands of reference materials covering every tech concept you need to stay up to date.
Subscribe now
View plans & pricing

Product Details

Publication date : Sep 08, 2015
Length: 158 pages
Edition : 1st
Language : English
ISBN-13 : 9781784398767
Languages :
Tools :

Packt Subscriptions

See our plans and pricing
Modal Close icon
$19.99 billed monthly
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Simple pricing, no contract
$199.99 billed annually
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just $5 each
Feature tick icon Exclusive print discounts
$279.99 billed in 18 months
Feature tick icon Unlimited access to Packt's library of 7,000+ practical books and videos
Feature tick icon Constantly refreshed with 50+ new titles a month
Feature tick icon Exclusive Early access to books as they're written
Feature tick icon Solve problems while you work with advanced search and reference features
Feature tick icon Offline reading on the mobile app
Feature tick icon Choose a DRM-free eBook or Video every month to keep
Feature tick icon PLUS own as many other DRM-free eBooks or Videos as you like for just $5 each
Feature tick icon Exclusive print discounts

Frequently bought together


Stars icon
Total $ 115.97
Symfony2 Essentials
$32.99
Mastering Symfony
$43.99
Extending Symfony2 Web Application Framework
$38.99
Total $ 115.97 Stars icon

Table of Contents

11 Chapters
1. The Symfony Framework – Installation and Configuration Chevron down icon Chevron up icon
2. Your First Pages Chevron down icon Chevron up icon
3. Twig Templating and Assets Handling Chevron down icon Chevron up icon
4. Forms Chevron down icon Chevron up icon
5. Security and Handling Users Chevron down icon Chevron up icon
6. Translation Chevron down icon Chevron up icon
7. AJAX Chevron down icon Chevron up icon
8. Command-line Operations Chevron down icon Chevron up icon
9. Symfony2 Profiler and Debugger Chevron down icon Chevron up icon
10. Preparing an Application for Production Chevron down icon Chevron up icon
Index Chevron down icon Chevron up icon

Customer reviews

Top Reviews
Rating distribution
Full star icon Full star icon Half star icon Empty star icon Empty star icon 2.7
(7 Ratings)
5 star 0%
4 star 28.6%
3 star 28.6%
2 star 28.6%
1 star 14.3%
Filter icon Filter
Top Reviews

Filter reviews by




Madchu Oct 08, 2017
Full star icon Full star icon Full star icon Full star icon Empty star icon 4
It took me two attempts to get through this, but that was mainly because I've been trying to learn everything and Symfony, at first glance, was a little daunting. The author covers things well, though, so I'm glad I gave this a second go. it complements well with an online course on Symfony from KNP University which is the best I've found so far on the subject.
Amazon Verified review Amazon
AlberT Nov 08, 2016
Full star icon Full star icon Full star icon Full star icon Empty star icon 4
Un libro che scorre facilmente, affronta più o meno tutti gli aspetti del ciclo di vita di una applicazione symfony ..Nulla di particolarmente illuminante, ma sicuramente una buona infarinatura generale.
Amazon Verified review Amazon
D. Cullen Feb 21, 2017
Full star icon Full star icon Full star icon Empty star icon Empty star icon 3
Mistakes in the examples make it tricky for someone completely new to symfony, but otherwise ok.
Amazon Verified review Amazon
Spurgeon Jun 07, 2016
Full star icon Full star icon Full star icon Empty star icon Empty star icon 3
Good book for experienced PHP developers to acquaint themselves with Symfony. Considering that Symfony 3 is out some time back, this might be slightly outdated. Nevertheless, the foundations / fundamentals hold good.
Amazon Verified review Amazon
Amazon Customer Feb 15, 2016
Full star icon Full star icon Empty star icon Empty star icon Empty star icon 2
very basic book, you could find better guides on the web.
Amazon Verified review Amazon
Get free access to Packt library with over 7500+ books and video courses for 7 days!
Start Free Trial

FAQs

What is included in a Packt subscription? Chevron down icon Chevron up icon

A subscription provides you with full access to view all Packt and licnesed content online, this includes exclusive access to Early Access titles. Depending on the tier chosen you can also earn credits and discounts to use for owning content

How can I cancel my subscription? Chevron down icon Chevron up icon

To cancel your subscription with us simply go to the account page - found in the top right of the page or at https://subscription.packtpub.com/my-account/subscription - From here you will see the ‘cancel subscription’ button in the grey box with your subscription information in.

What are credits? Chevron down icon Chevron up icon

Credits can be earned from reading 40 section of any title within the payment cycle - a month starting from the day of subscription payment. You also earn a Credit every month if you subscribe to our annual or 18 month plans. Credits can be used to buy books DRM free, the same way that you would pay for a book. Your credits can be found in the subscription homepage - subscription.packtpub.com - clicking on ‘the my’ library dropdown and selecting ‘credits’.

What happens if an Early Access Course is cancelled? Chevron down icon Chevron up icon

Projects are rarely cancelled, but sometimes it's unavoidable. If an Early Access course is cancelled or excessively delayed, you can exchange your purchase for another course. For further details, please contact us here.

Where can I send feedback about an Early Access title? Chevron down icon Chevron up icon

If you have any feedback about the product you're reading, or Early Access in general, then please fill out a contact form here and we'll make sure the feedback gets to the right team. 

Can I download the code files for Early Access titles? Chevron down icon Chevron up icon

We try to ensure that all books in Early Access have code available to use, download, and fork on GitHub. This helps us be more agile in the development of the book, and helps keep the often changing code base of new versions and new technologies as up to date as possible. Unfortunately, however, there will be rare cases when it is not possible for us to have downloadable code samples available until publication.

When we publish the book, the code files will also be available to download from the Packt website.

How accurate is the publication date? Chevron down icon Chevron up icon

The publication date is as accurate as we can be at any point in the project. Unfortunately, delays can happen. Often those delays are out of our control, such as changes to the technology code base or delays in the tech release. We do our best to give you an accurate estimate of the publication date at any given time, and as more chapters are delivered, the more accurate the delivery date will become.

How will I know when new chapters are ready? Chevron down icon Chevron up icon

We'll let you know every time there has been an update to a course that you've bought in Early Access. You'll get an email to let you know there has been a new chapter, or a change to a previous chapter. The new chapters are automatically added to your account, so you can also check back there any time you're ready and download or read them online.

I am a Packt subscriber, do I get Early Access? Chevron down icon Chevron up icon

Yes, all Early Access content is fully available through your subscription. You will need to have a paid for or active trial subscription in order to access all titles.

How is Early Access delivered? Chevron down icon Chevron up icon

Early Access is currently only available as a PDF or through our online reader. As we make changes or add new chapters, the files in your Packt account will be updated so you can download them again or view them online immediately.

How do I buy Early Access content? Chevron down icon Chevron up icon

Early Access is a way of us getting our content to you quicker, but the method of buying the Early Access course is still the same. Just find the course you want to buy, go through the check-out steps, and you’ll get a confirmation email from us with information and a link to the relevant Early Access courses.

What is Early Access? Chevron down icon Chevron up icon

Keeping up to date with the latest technology is difficult; new versions, new frameworks, new techniques. This feature gives you a head-start to our content, as it's being created. With Early Access you'll receive each chapter as it's written, and get regular updates throughout the product's development, as well as the final course as soon as it's ready.We created Early Access as a means of giving you the information you need, as soon as it's available. As we go through the process of developing a course, 99% of it can be ready but we can't publish until that last 1% falls in to place. Early Access helps to unlock the potential of our content early, to help you start your learning when you need it most. You not only get access to every chapter as it's delivered, edited, and updated, but you'll also get the finalized, DRM-free product to download in any format you want when it's published. As a member of Packt, you'll also be eligible for our exclusive offers, including a free course every day, and discounts on new and popular titles.