1-33

Symfony2 – Franz Jordán 2011
Like the {slug} placeholder before, the value matching {page} will be available inside your
controller. Its value can be used to determine which set of blog posts to display for the given
page.
But hold on! Since placeholders are required by default, this route will no longer match on
simply/blog. Instead, to see page 1 of the blog, you'd need to use the URL /blog/1! Since
that's no way for a rich web app to behave, modify the route to make the {page} parameter
optional. This is done by including it in the defaults collection:
blog:
pattern: /blog/{page}
defaults: { _controller: AcmeBlogBundle:Blog:index, page: 1 }
By adding page to the defaults key, the {page} placeholder is no longer required. The
URL /blogwill match this route and the value of the page parameter will be set to 1. The
URL /blog/2 will also match, giving the page parameter a value of 2. Perfect.
/blog {page} = 1
/blog/1 {page} = 1
/blog/2 {page} = 2
Adding Requirements
Take a quick look at the routes that have been created so far:
blog:
pattern: /blog/{page}
defaults: { _controller: AcmeBlogBundle:Blog:index, page: 1 }
blog_show:
pattern: /blog/{slug}
defaults: { _controller: AcmeBlogBundle:Blog:show }
Can you spot the problem? Notice that both routes have patterns that match URL's that look
like/blog/*. The Symfony router will always choose the first matching route it finds. In other
words, theblog_show route will never be matched. Instead, a URL like /blog/my-blogpost
will match the first route (blog) and return a nonsense value of my-blog-post to
the {page} parameter.
URL
route parameters
/blog/2 blog {page} = 2
/blog/my-blog-post blog
{page} = my-blog-post
The answer to the problem is to add route requirements. The routes in this example would work
perfectly if the /blog/{page} pattern only matched URLs where the {page} portion is an
59