Metadata: Add filter for custom taxonomies #1995
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
acicovic
approved these changes
Nov 10, 2023
acicovic
reviewed
Nov 13, 2023
acicovic
changed the title
|
@norcross, this will become available in the 3.11.0 release. |
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
This change adds a filter to the array of non-default (i.e. custom) taxonomies being passed.
Motivation and context
Currently, the option to include categories into the larger array is an "all or nothing" choice. many site used custom taxonomies for reasons that don't require being included, much like the existing core function that removes the
authortaxonomy added by Co-Authors Plus.this PR is in response to this: #1970 (a coworker of mine)
How has this been tested?
We tested these changes locally and on our VIP environments, and have deployed a similar fix to our production site.
This was run using the most current version of the plugin (3.10.0)