Cache core and plugin updates #856
Open
Conversation
This file contains hidden or 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
1 participant
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.
Keeps track of pending plugin and core updates.
Plugins are checked on date set in the
plugin_update_last_checkoption. Plugin IDs and versions are stored in theplugin_update_cacheoption, as JSON. Only updates are stored. It could be possible to use one option to store everything and include the last check date (as the core, below). I'm inclined to keep the rows used to the minimum, as long as they make sense.The core works in the same way but the last check is stored in the same option row as the version and they are stored as a JSON object as well.
The approach invalidates the cache as discussed here: #769 (comment)