-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
querying acf relationship fields between CPT and Product returns an error #565
Comments
Hi @vstrelianyi can you post your Custom Field configuration? I'm wondering if you have the |
Hi @ardiewen ! |
btw I have found the same issue here in acf graphql plugin repo |
Yeah interesting... definitely related to the acf schema filter as mentioned in the other post. However the solve seems to be on this repo. I will see if I can test a potential fix. |
That would be great! Thx a lot! |
Hi @vstrelianyi, you'll need two PRs to fix the issue: #568 on this repo Please note the following:
|
Ok. will try that!, thx! |
I think only |
@vstrelianyi @CesarBenavides777 @ardiewen @asmartbear Is this still an issue in |
@kidunot89 Let me get this tested and confirm. |
versions:
WP 5.8.1
Woo 5.8.0
Graphql 1.6.5
WPGraphQL WooCommerce 0.10.4
Advanced Custom Fields PRO 5.10.2
WPGraphQL for Advanced Custom Fields 0.5.3
Steps:
QUERY:
ERROR:
QUERY:
query GET_AUCTIONS {
auctions {
nodes {
title
acf_auctions {
auctionProduct {
... on SimpleProduct {
id
name
databaseId
commentCount
}
}
}
}
}
}
ERROR:
{
"errors": [
{
"message": "Internal server error",
"extensions": {
"category": "internal"
},
"locations": [
{
"line": 6,
"column": 9
}
],
"path": [
"auctions",
"nodes",
1,
"acf_auctions",
"auctionProduct",
0
]
}
],
"data": {
"auctions": {
"nodes": [
{
"title": "Auction 2",
"acf_auctions": {
"auctionProduct": null
}
},
{
"title": "Auction 1",
"acf_auctions": {
"auctionProduct": [
null
]
}
}
]
}
},
"extensions": {
"debug": [
{
"type": "DEBUG_LOGS_INACTIVE",
"message": "GraphQL Debug logging is not active. To see debug logs, GRAPHQL_DEBUG must be enabled."
}
]
}
}
The text was updated successfully, but these errors were encountered: