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

Menu filters not working with wordpress-source-experimental plugin #39

Open
tiggeymone opened this issue Feb 5, 2021 · 4 comments
Open

Comments

@tiggeymone
Copy link

Hello, thank you for this awesome plugin.

I just figured out that I can filter menu items by language when using the WPGraphiql plugin IDE:
Screenshot 2021-02-05 at 19 17 52

Unfortunately the same filter seems to be unavailable using the gatsby-source-wordpress-experimental plugin. The language filter works for all the other types, such as posts, pages etc:

Screenshot 2021-02-05 at 19 19 09

Is there any reason why the wordpress-source-experimental plugin isn't recognizing this filter?

Thank you in advance

@esamattis
Copy link
Member

To my knowledge gatsby-source-wordpress-experimental uses the graphql fields exposed by wp-graphql so it should just work, but I have not used gatsby-source-wordpress-experimental so I'm not sure it does something weird before it calls the wp-graphql fields.

@dannyvaughton
Copy link

dannyvaughton commented Mar 30, 2021

I am having the same issue.

However, I am using their new gatsby-source-wordpress release

@tiggeymone
Copy link
Author

Hello, I created an issue in the gatsby monorepo, because the new gatsby-source-wordpress plugin is now included within it. You can find the issue here: gatsbyjs/gatsby#30597. I've found that the problem is not just on menu items, but also in some other content types, such as contentNodes. This makes really difficult to create a query scoped by language for multiple post types that should support pagination.

Assuming that most of the filters are correctly introspected by gatsby-source-wordpress, IMHO it could be some problem related on how some fields are exposed by this plugin.

Any kind of help will be really appreciated!

Thank you in advance

@sidyes
Copy link

sidyes commented Jan 15, 2022

Any updates on this one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants