Skip to content

ensure consistency of Symfony and standalone session code block #20097

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 1 commit into from
Aug 6, 2024
Merged

ensure consistency of Symfony and standalone session code block #20097

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
12 changes: 5 additions & 7 deletions session.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,15 +171,13 @@ For example, imagine you're processing a :doc:`form </forms>` submission::

// add flash messages
$flashes->add(
'warning',
'Your config file is writable, it should be set read-only'
'notice',
'Your changes were saved'
);
$flashes->add('error', 'Failed to update name');
$flashes->add('error', 'Another error');

After processing the request, the controller sets a flash message in the session
and then redirects. The message key (``warning`` and ``error`` in this example) can be anything:
you'll use this key to retrieve the message.
After processing the request, the controller sets a flash message in the
session and then redirects. The message key (``notice`` in this example)
can be anything. You'll use this key to retrieve the message.

In the template of the next page (or even better, in your base layout template),
read any flash messages from the session using the ``flashes()`` method provided
Expand Down
Loading