-
Notifications
You must be signed in to change notification settings - Fork 18
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
Issue with orderBy and cursor pagination #12
Comments
Same issue here, did you find any solution? |
This is probably an upstream issue with wp-graphql. I don't have the time to look into this currently but if anybody would like to help the first thing would be to extract the args wp-graphql-meta-query generates for WP_Query so we could write a test case for it. There are already few numeric ordering tests by meta value But maybe we're missing something 🤔 |
I get this error when I try to order on a CPT using TITLE or any other sort field. I will set up a CodeSanbox to show the issue. |
This happened to me when i was sorting on a "non indexed" column |
Don't know if this is something related to this plugin (i'd rather say that it belongs to
wp-graphql
) but still, i prefer to write it here; if is the case, i can move the issue.I'm having issues when i want to sort elements by a certain
META
field value and using together the pagination cursor. Example:For this query:
I'm getting this result:
I want to order them by the
orderField
, so, for this query:i get this:
which is what i'm expecting. Now, i want to use the cursor pagination, so i made this query:
and i would expect to receive the other 2 items, but instead i get this:
i guess this is because the default
sort
field is theDATE
, and the element with theorderField: 2
is the last one, so there're no more items after that last one.The text was updated successfully, but these errors were encountered: