support "disallowed_keys" instead of "blacklist" for WP 5.5 compat #174
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
The "comment blacklist" has been renamed to "disallowed comment keys" along with the corresponding option key. We now support the new option, if available. Also the frontend wording is adapted to match the new labels.
patrickrobrecht
approved these changes
Jul 25, 2020
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.
In WordPress 5.5 the "comment blacklist" has been renamed to "disallowed comment keys" along with the corresponding option key1.
We now support the new option, if available.
Also the frontend wording is adapted to match the new labels.
Private methods and comments changed where reasonable. Public methods and internal option names left untouched for backwards compatibility.
[1] https://make.wordpress.org/core/2020/07/23/codebase-language-improvements-in-5-5/