Skip to content

Reworded the note about dump() availability per environment #8967

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.

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

Closed
wants to merge 2 commits into from
Closed
Changes from 1 commit
Commits
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
9 changes: 4 additions & 5 deletions templating/debug.rst
Original file line number Diff line number Diff line change
Expand Up @@ -46,8 +46,7 @@ The same mechanism can be used in Twig templates thanks to ``dump()`` function:
</a>
{% endfor %}

By design, the ``dump()`` function is only available if the ``kernel.debug``
setting (in ``config.yml``) is ``true``, to avoid leaking sensitive information
in production. In fact, trying to use the ``dump()`` function when ``kernel.debug``
is ``false`` (for example in the ``prod`` environment) will result in an
application error.
By design, the ``dump()`` function is only available if the ``dev`` and ``test``
environments, to avoid leaking sensitive information in production. In fact,
trying to use the ``dump()`` function in the ``prod`` environment will result in
an application exception.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"application exception" -> "php error" (call undefined function ...)