Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit925267d

Browse files
committed
Minor typos in session articles
1 parentd464e84 commit925267d

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

‎session/locale_sticky_session.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ Making the Locale "Sticky" during a User's Session
55
==================================================
66

77
Symfony stores the locale setting in the Request, which means that this setting
8-
is notautomtically saved ("sticky") across requests. But, you *can* store the locale
8+
is notautomatically saved ("sticky") across requests. But, you *can* store the locale
99
in the session, so that it's used on subsequent requests.
1010

1111
.. _creating-a-LocaleSubscriber:

‎session/php_bridge.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,7 +90,7 @@ the example below:
9090
override this. Instead set ``handler_id: ~``. Note that a save handler
9191
cannot be changed once the session has been started. If the application
9292
starts the session before Symfony is initialized, the save handler will
93-
have already beenset. In this case, you will need ``handler_id: ~``.
93+
have already been set. In this case, you will need ``handler_id: ~``.
9494
Only override the save handler if you are sure the legacy application
9595
can use the Symfony save handler without side effects and that the session
9696
has not been started before Symfony is initialized.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp