-
Notifications
You must be signed in to change notification settings - Fork 46
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
Updated 4.0 release #72
Closed
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
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.
Introduces some better protection against race conditions:
plugins_loaded
action, making the latter an improper place to wire in the creation of a new session (as the DB didn't exist). Instead, we'll just ensure the DB is up to date on both hooks (this way a CLI-based install will still trigger the creation of the table, but a browser-based install won't trigger an error either).$wpdb
global was available. We'll ensure this global is non-null before attempting to use it.This version also introduces a cache-based session handler. If a site is leveraging Memcached or Redis (or even APC) then encrypted session data will be stored there as well. This way, WordPress only has to go to the cache and not all the way to the database to grab source data.
Target for release is Tuesday, January 1, 2019.