1-33

Symfony2 – Franz Jordán 2011
The routes from this file are parsed and loaded in the same way as the main routing file.
Prefixing Imported Routes
You can also choose to provide a "prefix" for the imported routes. For example, suppose you
want the acme_hello route to have a final pattern of /admin/hello/{name} instead of
simply/hello/{name}:
# app/config/routing.yml
acme_hello:
resource: "@AcmeHelloBundle/Resources/config/routing.yml"
prefix: /admin
The string /admin will now be prepended to the pattern of each route loaded from the new
routing resource.
Visualizing & Debugging Routes
While adding and customizing routes, it's helpful to be able to visualize and get detailed
information about your routes. A great way to see every route in your application is via
the router:debug console command. Execute the command by running the following from the
root of your project.
php app/console router:debug
The command will print a helpful list of all the configured routes in your application:
homepage ANY /
contact GET /contact
contact_process POST /contact
article_show ANY /articles/{culture}/{year}/{title}.{_format}
blog ANY /blog/{page}
blog_show ANY /blog/{slug}
You can also get very specific information on a single route by including the route name after
the command:
php app/console router:debug article_show
Generating URLs
The routing system should also be used to generate URLs. In reality, routing is a bi-directional
system: mapping the URL to a controller+parameters and a route+parameters back to a URL.
Thematch() and generate() methods form this bi-directional system. Take
the blog_show example route from earlier:
$params = $router->match('/blog/my-blog-post');
// array('slug' => 'my-blog-post', '_controller' => 'AcmeBlogBundle:Blog:show')
$uri = $router->generate('blog_show', array('slug' => 'my-blog-post'));
// /blog/my-blog-post
64