-
Notifications
You must be signed in to change notification settings - Fork 122
Duplicate type registration errors when enabling field groups only on specific posts #198
Comments
Wrong repo. |
Re-opening, seems to be an issue with this ACF plugin (disabling plugin gets rid of the duplicate type registration errors). |
This might be a duplicate of #189 |
Temporary solution (as described here #189 (comment)) is to assign the field group based on post type as opposed to specific posts. |
I've reproduced this with the following location rules: The issue here is that the field group is created and registered to the We've been discussing changing how location rules are handled, and instead of inferring location rules and mapping to the Schema the plan is to have a more explicit UI where users can define the specific Type(s) in the Schema where an ACF Field group should be available. |
This is resolved by #250. I can now create a field group that contains a "Link" field type, and assign it to Posts and Pages: Then query the field and get no debug message in the debug logs. No more |
My queries are still executing but when I enable debugging I see a huge list of "duplicate type" errors, which seems like my custom post type "component" is having its GQL types registered more than once.
See errors in example server GQL response: https://gist.github.com/benknight/baab7b0842694bff54e096835d727803
Here's how the post type is being registered:
Versions:
The text was updated successfully, but these errors were encountered: