1. Routing, Controllers & Templates

2. Route
● A route is a map from a URL path to a
controller.
● defined in the app/config/routing.yml
configuration file.
● When you're in the dev environment - indicated by
the app_**dev**.php front controller - the
app/config/routing_dev.yml configuration file is
also loaded.

3. Basic Route Configuration¶

4. ● Symfony2 chooses the controller based on the
_controller value from the routing configuration:
● AcmeDemoBundle:Welcome:index
– controller logical name
● indexAction method from
– AcmeDemoBundleControllerWelcomeController.php class
– can also be written as:
● AcmeDemoBundleControllerWelcomeController::indexAction

5. Inside:
src/Acme/DemoBundle/Controller/W
elcomeController.php

6. Routing: Under the Hood

7. Other Examples

8. Routing with Placeholders
For example, suppose you want to match any
URL like:
/blog/my-post
or
/blog/all-about-symfony

10. Required and Optional Placeholders

11. Possible Problem

12. Adding Requirements
For other requirement options, please refer to:
http://symfony.com/doc/current/book/routing.html

13. Using annotations

16. Including External Routing
Resources¶

17. Prefixing Imported Routes

18. Visualizing & Debugging Routes
● $ php app/console router:debug
●
● $ php app/console router:debug article_show
●
● $ php app/console router:match /blog/my-latest-
post

20. Controllers

21. Controller
● A controller is a PHP function you create that
takes information from the HTTP request and
constructs and returns an HTTP response (as a
Symfony2 Response object).
● The response could be an HTML page, an XML
document, a serialized JSON array, an image, a
redirect, a 404 error or anything else you can dream
up.

22. A Simple Controller

23. Route Parameters as Controller Arguments

24. Route Parameters as Controller Arguments
● The order of the controller arguments does not matter
● Each required controller argument must match up with a routing
parameter
●

25. The Request as a Controller
Argument

26. The Base Controller Class

27. Common Controller Tasks

28. Redirecting

29. Forwarding

30. Rendering Templates¶

31. Managing Errors and 404 Pages

32. Generating URLs

33. Generating Absolute URLs

34. Generating URLs with Query Strings

35. Templates

36. Templates
● A template is simply a text file that can generate
any text-based format (HTML, XML, CSV,
LaTeX …)
● Commonly-used in Symfony:
● PHP template
● Twig template

37. Template Locations
● By default, templates can live in two different
locations:
● app/Resources/views/
– The applications views directory can contain application-
wide base templates
● path/to/bundle/Resources/views/(controller)
– Each bundle houses its templates in its Resources/views
directory (and subdirectories).

38. Template Suffix
● index.html.twig
● HTML format, Twig engine
● index.html.php
● HTML format, PHP engine
● index.txt.twig
● TXT format, Twig engine

39. To render a template in Symfony
● Symfony2 uses a bundle:controller:template
string syntax for templates.
●
src/Acme/DemoBundle/Resources/views/Demo/hello.html.twig.

40. PHP template
● a text file parsed by PHP that contains a mix of
text and PHP code

41. Twig templates
● Twig allows you to write concise, readable
templates that are more friendly to web
designers and, in several ways, more powerful
than PHP templates

42. Twig defines 3 kinds of delimiters:
● {{ }}
● Prints a variable or the result of an expression;
● {% %}
● Controls the logic of the template; it is used to
execute for loops and if statements, for example.
● {# #}
● Comments can be included inside templates

43. Variables passed to a template can
be strings, arrays, or even objects.

44. Template Inheritance and Layouts
● template inheritance allows you to build a base
"layout" template that contains all the common
elements of your site defined as blocks.
● A child template can extend the base layout
and override any of its blocks.

45. simple parent and child
NOTE: Body content is not allowed in the child.

46. complex parent

47. complex child

48. sample result:

49. Tips
● If you use {% extends %} in a template, it must be the first tag in
that template;
● The more blocks your base templates have, the more flexible
your layout will be;
●
● If you need to get the content of a block from the parent
template, you can use the {{ parent() }} function.

50. Including other Templates
● The best way to share a snippet of code
between several distinct templates

51. Another example:

52. Embedding other Controllers
● what if you want to embed the result of another
controller in a template?

53. Includee: Controller + template

54. Includer: template

55. Creating Links between Pages
● href=”/”
● FULL PATH
●
href=”http://localhost/Symfony/web/app_dev.php”

56. Creating Links between Pages
● href=”/article/this-is-a-sample-title”

57. Including Assets: images,
JavaScripts, and stylesheets

58. Convention: parent

59. Convention: child

60. Back to you RC