-
Notifications
You must be signed in to change notification settings - Fork 154
fix: correctly detect ACF taxonomies by checking post_content #1748
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
Open
arifulhoque7
wants to merge
4
commits into
weDevsOfficial:develop
Choose a base branch
from
arifulhoque7:fix/acf-taxonomy-free-version-support
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
bb1fc6b
fix: correctly detect ACF taxonomies by checking post_content
arifulhoque7 62bdbec
Add function to get taxonomy post types and update free taxonomies logic
arifulhoque7 a95e20f
Merge branch 'develop' into fix/acf-taxonomy-free-version-support
arifulhoque7 9fb0e06
Remove ACF taxonomy check function
arifulhoque7 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify the fallback to
taxonomykey is necessary.Line 571 extracts the taxonomy slug with
$f['name'] ?? ($f['taxonomy'] ?? null), falling back to thetaxonomykey. However, the other methods (filter_pro_taxonomy_fieldsandget_hidden_taxonomy_ids) only check$field['name'].Ensure this fallback is intentional and that taxonomy fields can indeed have the slug under either key, or consider aligning the extraction logic across all three methods for consistency.
🏁 Script executed:
Length of output: 16231
🏁 Script executed:
Length of output: 4029
🏁 Script executed:
Length of output: 3215
Align the taxonomy slug extraction with other methods for consistency.
Line 571 extracts the slug with a fallback to
$f['taxonomy'], butfilter_pro_taxonomy_fields(line 528) andget_hidden_taxonomy_ids(line 607) only check$field['name']. Since all observed field definitions consistently populate thenamekey, the fallback appears unnecessary. Either document why thetaxonomykey fallback is needed for nested fields, or remove it to align with the other methods.🤖 Prompt for AI Agents