Skip to content
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

User field is returning all users #162

Closed
2 of 3 tasks
jasonbahl opened this issue Feb 1, 2024 · 0 comments · Fixed by #165
Closed
2 of 3 tasks

User field is returning all users #162

jasonbahl opened this issue Feb 1, 2024 · 0 comments · Fixed by #165
Assignees
Labels
status: actionable Ready for work to begin type: bug Issue that causes incorrect or unexpected behavior

Comments

@jasonbahl
Copy link
Contributor

Description

When querying the Users field, all users are being returned instead of just the users selected on the field.

Steps to reproduce

  1. create an ACF Field group with a field of the "user" type
  2. assign the field group to pages
  3. Edit a page, selecting one or more users on the user field
  4. Update/Publish the page
  5. Query for the page and the user field
  6. see that all users are returned, not just the selected user(s)

Selected:
CleanShot 2024-02-01 at 08 53 48

Query:
CleanShot 2024-02-01 at 08 54 25

PHP or JSON export of the ACF Field Group(s)

acf-export-2024-02-01.json.zip

Additional context

No response

WPGraphQL Version

1.20.0

WPGraphQL For ACF Version

2.1.0

ACF (Advanced Custom Fields) Version. Free or Pro?

Latest, PRO

WordPress Version

latest

PHP Version

8.1

Additional enviornment details

No response

Please confirm that you have searched existing issues in the repo.

  • Yes

Please confirm that you have disabled ALL plugins except for WPGraphQL, WPGraphQL For ACF, ACF, etc.

  • Yes
  • My issue is with compatibility with a specific WordPress plugin, and I have listed all my installed plugins (and version info) above.
@jasonbahl jasonbahl self-assigned this Feb 1, 2024
@jasonbahl jasonbahl added the status: actionable Ready for work to begin label Feb 1, 2024
@ChrisWiegman ChrisWiegman added the type: bug Issue that causes incorrect or unexpected behavior label Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: actionable Ready for work to begin type: bug Issue that causes incorrect or unexpected behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants