Add DB-backed WP_Session_Tokens implementation #345
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Draft support for this in the TracWordPressCookiesPlugin: dd32/TracWordPressCookiesPlugin#2 - I haven't tested this in my test trac environment, but it looks like it'll work and is much simpler than the user_meta implementation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WordPress sessions (Which are not used on WordPress.org currently) use user-meta to store active user sessions.
This class, based on the implementation on WordPress.com, stores these sessions in a custom table.
This is pending changes to allow the use of sessions on WordPress.org, such as dealing with Trac
and the Codexthe codex doesn't share cookies, only user tables..This is preferably needed so that we can use the upstream 2fa session code for WordPress/wporg-two-factor#43