You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So depending on where you use GutenbergBlocks in the GQL document, it will break nextPost or previousPost queries.
For example, previousPost and nextPost will be null when accessed like this:
#import "~/gql/fragments/GutenbergBlocks.gql"
query NewsDetail($uri: String!) {
nodeByUri(uri: $uri) {
id
... on Post {
...GutenbergBlocks
previousPost {
node {
... on Post {
id
}
}
}
nextPost {
node {
... on Post {
id
}
}
}
}
}
}
@drewbaker I can't replicate the error on my end. I test it on my local, but it works fine on my local.
Could you provide me the Post content so that I can test it correctly.
Thanks!
I think this is going to be a hard thing to debug, because it probably depends on the contents of the blocks... next time I run into it I will capture here.
So depending on where you use GutenbergBlocks in the GQL document, it will break nextPost or previousPost queries.
For example,
previousPost
andnextPost
will be null when accessed like this:But if you move
...GutenbergBlocks
to be afternextPost
then they work fine. This might be related this function in our theme, but I doubt it: https://github.com/funkhaus/fuxt-backend/blob/master/functions/gql-functions.php#L229The text was updated successfully, but these errors were encountered: