Skip to content

DOC Document backporting non-blocking sessions #778

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

Open
wants to merge 1 commit into
base: 6
Choose a base branch
from
Open

DOC Document backporting non-blocking sessions #778

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
2 changes: 2 additions & 0 deletions en/08_Changelogs/6.1.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,6 +120,8 @@ See the [save handler documentation](/developer_guides/cookies_and_sessions/sess

Note that if you are using [`silverstripe/hybridsessions`](https://packagist.org/packages/silverstripe/hybridsessions) or [`silverstripe/dynamodb`](https://packagist.org/packages/silverstripe/dynamodb), you can continue to use these with no change, provided you update them to the latest version.

If you want this functionality in your CMS 5 projects, we have created a new [`silverstripe/non-blocking-sessions`](https://github.com/silverstripe/silverstripe-non-blocking-sessions) module that backports the file-based non-blocking session save handler to CMS 5.

### Password strength feedback

The [`ConfirmedPasswordField`](api:SilverStripe\Forms\ConfirmedPasswordField) now provides real-time feedback on password strength as users type. You'll see this in action on the member edit form, when setting a new password during the "lost password" process, and for any usages of `ConfirmedPasswordField` in your own forms if [`requireStrongPassword`](api:SilverStripe\Forms\ConfirmedPasswordField->requireStrongPassword) is toggled on.
Expand Down