-
Notifications
You must be signed in to change notification settings - Fork 21
Fix: Display Taxonomy Field data in user profiles #392
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
base: develop
Are you sure you want to change the base?
Changes from 3 commits
97a50b0
a2c334e
ed6f669
76debad
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,300 @@ | ||||||||||||
| <?php | ||||||||||||
| /** | ||||||||||||
| * Tests for the taxonomy field display fix (PR #392). | ||||||||||||
| * | ||||||||||||
| * When a WPUM field has type 'taxonomy' and its user_meta_key starts with | ||||||||||||
| * 'wpum_', the set_user_meta() method should retrieve the value via | ||||||||||||
| * get_user_meta() instead of carbon_get_user_meta(), because Carbon Fields | ||||||||||||
| * returns empty for taxonomy-type fields. | ||||||||||||
| * | ||||||||||||
| * The fix adds `&& $this->get_type() !== 'taxonomy'` to the elseif branch | ||||||||||||
| * in set_user_meta() so taxonomy fields fall through to the get_user_meta() | ||||||||||||
| * path. | ||||||||||||
| * | ||||||||||||
| * Note: The 'taxonomy' field type class (WPUM_Field_Taxonomy) lives in the | ||||||||||||
| * wpum-custom-fields addon, not core. These tests verify the branching logic | ||||||||||||
| * in set_user_meta() without requiring the addon to be active. | ||||||||||||
| * | ||||||||||||
| * @see https://github.com/WPUserManager/wp-user-manager/pull/392 | ||||||||||||
|
Comment on lines
+17
to
+18
|
||||||||||||
| * | |
| * @see https://github.com/WPUserManager/wp-user-manager/pull/392 |
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.
Copilot
AI
Feb 26, 2026
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.
The function wpum_passthrough_formatter is defined identically in two test methods (lines 221-225 and 258-262). While the function_exists() check prevents a fatal error, this is code duplication. Consider either: 1) Defining the function once in the test class setup method, 2) Using a shared helper method, or 3) Ensuring only one function definition exists and removing the duplicate from lines 258-262.
| if ( ! function_exists( 'wpum_passthrough_formatter' ) ) { | |
| function wpum_passthrough_formatter( $field, $value ) { | |
| return $value; | |
| } | |
| } |
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.
Fixed - removed the duplicate wpum_passthrough_formatter definition from the second test method. The function_exists() guard was masking the duplication.
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.
The header comment references "PR #392" but this appears to be a different PR. The comment should reference the correct PR number or be updated to avoid confusion.
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.
This is correct — the file documents tests for PR #392 (the taxonomy field display fix). The header comment accurately identifies which PR these tests belong to.