Skip to content

Fix how to safely use is_granted in error pages #2359

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

Merged
merged 2 commits into from
Mar 31, 2013
Merged

Fix how to safely use is_granted in error pages #2359

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
82b0009
Fix how to safely use is_granted in error pages
ftassi Mar 26, 2013
b2cd345
Fix app.user check
ftassi Mar 26, 2013
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
2 changes: 1 addition & 1 deletion cookbook/controller/error_pages.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ end-user, create a new template located at
by your error pages), because the router runs before the firewall. If
the router throws an exception (for instance, when the route does not
match), then using ``is_granted`` will throw a further exception. You
can use ``is_granted`` safely by saying ``{% if app.security and is_granted('...') %}``.
can use ``is_granted`` safely by saying ``{% if app.user is not null and is_granted('...') %}``.

.. tip::

Expand Down