Use wp_cache_flush_group() when available
#2916
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
4 tasks
|
If this could be treated with some urgency, we have been unable to upgrade beyond ElasticPress 3.6.6 Since 4.x with Object Cache Pro plugin exhibits run-away Memory Usage whilst indexing |
|
Thanks for the PR @tillkruss! I'll merge it now. For future reference, I'll leave here links to:
|
|
@felipeelia Sure thing, will do! 👍 |
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.
Description of the Change
Unsetting the group key in
$cacheis a shot in the dark, let's use WordPress 6.1 newwp_cache_flush_group()when availableFollow-up to #2915.
Changelog Entry
Credits
Props @tillkruss
Checklist: