Jason Bahl

@dylanesque43 how are you installing the plugin?

@laikathespacedog how are you installing version 1.3.4? Are you installing from www.remarpro.com or some other installation method?

@therealgilles the above query should return the first 10 categories associated with each post.

You can get more than 10 like so:

query MyQuery {
  posts(first: 10) {
    nodes {
      title
      categories(first:100) {
        nodes {
          name
        }
      }
    }
  }
}

If you need more than 100, you would need to paginate, or filter the server to allow more than 100 to be returned (not highly recommended as it can cause server processing issues).

		
	

@vadimtet we’ll need a lot more information to be able to provide support here.

What actions were you taking when you ran into the issue? What was the expected behavior? What was the actual behavior? What are the steps to reproduce?

The more information you can provide, the more better we can help identify the conflict and come to a resolution.

@jenish11 the {$postType}By (in your case workBy) field has been deprecated for quite some time.

If you want to query a post of a custom post type by uri, you can do so with:

{
  work( id:"/path/to/post" idType: URI ) {
    id
    ...otherFields
  }
}

• This reply was modified 3 years, 11 months ago by Jason Bahl.

It’s not currently. I’d be open to considering these entry points as default though!

Please open a Github issue (or add comments to an existing one, if there is one) to discuss further.

But for now, that extension is a great example to show how extendable the Graph is to add entry points for whatever situation you need!

Marking this resolved. v1.2.4 corrects the issue where the vendor directory wasn’t properly being deployed from Github to www.remarpro.com.

Sorry for the mistake. I had made changes to the Github -> www.remarpro.com deploy process, and accidentally had the vendor directory being ignored from deploys.

I got the deploys working properly again and installing from www.remarpro.com is working again.

If you’re seeing the error:

Error:
“WPGraphQL has been installed without dependencies. Try installing from www.remarpro.com or run “composer install” from the plugin directory to install dependencies”

You should be able to visit your sites /plugins.php page, delete wp-graphql and re-install the new version that’s been deployed with the vendor directory.

Tracking this here: https://github.com/wp-graphql/wp-graphql/issues/1743

Working on it right now. I broke something with the new WordPress deploy script that deploys to www.remarpro.com from Github.

Should have a fix shortly.

Nice!

We’ve got it listed on the WPGraphQL Extensions page!

https://www.wpgraphql.com/extenstion-plugins/wpgraphql-for-carbon-fields/

Thanks @matheuspaiva! Appreciate the kind words ??

@chamois_blanc I wrote up some docs about WPGraphQL Security here: https://www.wpgraphql.com/docs/security/

If you have any specific questions, please let us know!

@chamois_blanc Thanks for the callout here!

I’m working on adding this page right now. Do you have any specific questions you’d like addressed here?

Some topics I plan to cover on the page:

– GraphQL Schema Introspection
– Access Control Rights
– WPGraphQL Model Layer
– Authentication & Authorization
– Mutations

If you have anything specific you had questions about, please let us know!

Hello Justin!

Thanks for checking out WPGraphQL! Excited to have you exploring using WPGraphQL with modern JavaScript front-ends.

It looks like you’re trying to use Next.JS combined with Gatsby. Gatsby and Next are both JavaScript frameworks that largely aim to solve similar problems, but in different ways.

While it might be possible in some cases to use Gatsby and Next together, it’s likely very uncommon.

I’d recommend sticking with Next or Gatsby instead of trying to combine them in one project.

To get started with Gatsby + WPGraphQL, I recommend starting here: https://www.gatsbyjs.com/guides/wordpress/

To get started with Next + WPGraphQL, I recommend this tutorial: https://dev.to/kendalmintcode/configuring-wordpress-as-a-headless-cms-with-next-js-3p1o

@lhtorres2015 it looks like it might be a permalink issue.

I can see your GraphQL endpoint here: https://wp-icrco.com/?graphql