Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minor fixes for Quick Tour #16

Closed
wants to merge 1 commit into from
Closed

Minor fixes for Quick Tour #16

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions quick_tour/the_big_picture.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,9 +100,9 @@ very easy).

.. tip::
The sandbox defaults to YAML, but you can easily switch to XML or PHP by
editing the ``config/AppKernel.php`` file. You can switch now by looking at
the bottom of ``config/AppKernel.php`` for instructions (the tutorials show
the configuration for all supported formats).
editing the ``app/AppKernel.php`` file. You can switch now by looking at the
bottom of ``app/AppKernel.php`` for instructions (the tutorials show the
configuration for all supported formats).

.. index::
single: Routing
Expand Down
12 changes: 6 additions & 6 deletions quick_tour/the_controller.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,9 +183,9 @@ the ``router`` helper before. It takes the route name and an array of parameters
as arguments and returns the associated friendly URL.

You can also easily forward the action to another one with the ``forward()``
method. As for the ``$view['actions']`` helper, it makes an internal
sub-request, but it returns the ``Response`` object to allow for further
modification if the need arises::
method. As for the ``actions`` helper, it makes an internal sub-request, but it
returns the ``Response`` object to allow for further modification if the need
arises::

$response = $this->forward('HelloBundle:Hello:fancy', array('name' => $name, 'color' => 'green'));

Expand All @@ -210,7 +210,7 @@ to the ``Request`` object::

$request->request->get('page'); // get a $_POST parameter

In a template, you can also access the request object via the ``request``
In a template, you can also access the ``Request`` object via the ``request``
helper:

.. code-block:: html+php
Expand All @@ -234,7 +234,7 @@ from any controller::
// in another controller for another request
$foo = $this['request']->getSession()->get('foo');

// get/set the user culture
// set the user locale
$this['request']->getSession()->setLocale('fr');

You can also store small messages that will only be available for the very
Expand All @@ -251,5 +251,5 @@ Final Thoughts

That's all there is to it, and I'm not even sure we have spent the allocated
10 minutes. In the previous part, we saw how to extend the templating system
with helpers. But everything can extended or replaced in Symfony2 with
with helpers. But everything can be extended or replaced in Symfony2 with
bundles. That's the topic of the next part of this tutorial.