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

Cloning one field adds all fields of the cloned fields group to the cloning field group #78

Closed
2 of 3 tasks
jasonbahl opened this issue Aug 29, 2023 · 0 comments · Fixed by #88
Closed
2 of 3 tasks
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 cloning a single field, all fields of the cloned field's field group are being added to the GraphQL Schema on the cloning field group.

Steps to reproduce

  1. using ACF Pro, create an ACF Field Group with multiple fields
  2. create another ACF Field Group and clone 1 field from the first field group
  3. Inspect the Schema
  4. See that all fields from the first field group have been added to the 2nd field group in the schema

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

No response

Additional context

No response

WPGraphQL Version

1.15.0

WPGraphQL For ACF Version

2.0.0-beta.4.0.09

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

Pro, 6.1.7

WordPress Version

6.3.1

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 Sep 12, 2023
@jasonbahl jasonbahl added the type: bug Issue that causes incorrect or unexpected behavior label Sep 12, 2023
@jasonbahl jasonbahl added the status: actionable Ready for work to begin label Sep 14, 2023
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.

1 participant