Is your feature request related to a problem? Please describe. We are using woocommerce subscription products and bundle products, and as there is a feature in wp graphql woo that allows us to filter on a products type, we would like to be able to filter on the types subscription and bundle which is not possible at the moment.

Describe the solution you'd like Extend the ProductTypesEnum to allow bundle and subscription

I have made a mutation to update the customer's details, more specifically only the billing details. I passed in the same clientMutatuinId that gets generated when the user logs in. The mutation gets executed successfully and it returns the updated customer details. But the actual customers details do not get changed at all it just stays the same.

However, it does work in graphiql but not on my frontend next.js app.

UPDATE: This is no longer an issue on v0.6.0, I'll keep it open because it might still be relevant for you, feel free to close in case. I installed version from master v 0.6.1 downgrading to v 0.6.0 seemed to fix the issue for me

Describe the bug Getting NO SCHEMA AVAILABLE after activating this plugin in GraphiQL Ide. Everything was working fine until I activated Gql WooCommerce plugin. Deactivating it shows the schema back

To Reproduce Activate both plugins (wp-graphql and wp-graphql-woocommerce) and lookup for the schema or documentation in graphiql, both are empty

Expected behavior A clear and concise description of what you expected to happen.

Screenshots

Desktop (please complete the following information):

• OS: MacOs
• Browser Chrome
• Version: WP GraphQL: 0.14.0 WooGraphQL: 0.6.1

Additional context Add any other context about the problem here.

Just in case I tried to do run a query on products getting it from the documentation:

query MyQuery {
  products(first: 1) {
    edges {
      cursor
      node {
        id
        name
      }
    }
  }
}

And it responds 500

{
  "code": "internal_server_error",
  "message": "<p>There has been a critical error on your website.</p><p><a href=\"https://wordpress.org/support/article/debugging-in-wordpress/\">Learn more about debugging in WordPress.</a></p>",
  "data": {
    "status": 500
  },
  "additional_errors": []
}

Describe the bug I am using graphql for create orders from the postman. queries are working fine but I can't run any mutations there is always customer capability error. I am also sending the Bearer token in header to authenticate the customer

To Reproduce Steps to reproduce the behavior:

1. http://localhost:8888/testsite/graphql or https://woographql.axistaylor.com/graphql
2. Headers Content-Type:application/graphql Authorization:Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJodHRwczpcL1wvd29vZ3JhcGhxbC5heGlzdGF5bG9yLmNvbSIsImlhdCI6MTU3MDAyMTg1OCwibmJmIjoxNTcwMDIxODU4LCJleHAiOjE1NzAwMjIxNTgsImRhdGEiOnsidXNlciI6eyJpZCI6IjMifX19.7drzb9beicfl-SqbPZvzseBGoY4Cf30eoS0x1wyGQIE
3. run this mutation

mutation MyMutation {
createOrder(input: {clientMutationId: "CreateOrder", customerId: 6, paymentMethod: "bacs", paymentMethodTitle: "Direct Bank Transfer", billing: {address1: "969 Market", city: "San Francisco", address2: "", company: "", country: US, email: "[email protected]", firstName: "John", lastName: "Doe", phone: "12903402832", postcode: "94103", state: "CA"}, shippingLines: {methodId: "flat_rate", methodTitle: "flat_rate", total: "10"}, shipping: {address1: "969 Market", address2: "", city: "San Francisco", country: US, email: "[email protected]", firstName: "JOhn", lastName: "Doe", phone: "180923843204", postcode: "94103", state: "CA"}, isPaid: true, lineItems: {productId: 30, quantity: 1}}) {
  clientMutationId
  order {
    cartHash
    currency
  }
}
}

Expected behavior The order should be created

Screenshots Request Screenshot

Screenshot 2 Screenshot 3

Describe the bug Attaching a product relationship within a Flexible content ACF field on to a Page post type renders an Abstract type error due to the resolve. The resolve is expected to resolve to an Object type.

To Reproduce Steps to reproduce the behavior:

1. ACF JSON Export File OR Create a new ACF Field Group (named WPGraphQL Example) with a Location > Rules equal to Page Add a Flexible Content (named Flexible Content) Field Type: Relationship (Layout name: Relationship Field, Field Label: Product Relationship) Filter by Post Type: Product Filter by Taxonomy: Simple (optional) Filters: All Checked Elements: Featured Image Checked Return Object: Post Object Save.

2. Navigate to Pages Choose a page: Home (take note of page ID) Add ACF Flexible Content Relationship Field Select 1+ products Save

3. Navigate to GraphiQL IDE > Add GraphQL statement (GraphQL Statement) OR

query PageById($id: Int!) {
  pageBy(pageId: $id) {
    id
    isFrontPage
    wpgraphqlExample {
      flexibleContent {
        ... on Page_Wpgraphqlexample_FlexibleContent_RelationshipField {
          fieldGroupName
          productRelationship {
            ... on SimpleProduct {
              id
              name
            }
          }
        }
      }
    }
  }
}

// Query Variables

{"id": 33}

4. Press Play > See error

Expected behavior A list of product objects

Screenshots

Desktop (please complete the following information):

• OS: macOS Big Sur 11.2.1
• Browser Chrome
• Version 88.0.4324.182 (Official Build) (x86_64)

Plugin Versions

• WooGraphQL Version: 0.6.1
• WPGraphQL Version: 1.2.5
• WordPress Version: 5.6.2 (Bedrock)
• WooCommerce Version: 4.8.0
• WPGraphQL for Advanced Custom Fields: 0.3.5
• WPGraphQL JWT Authentication: 0.4.1
• Disable Gutenberg: 2.4
• Safe SVG: 1.9.9
• WooCommerce Accommodation Bookings: 1.1.23
• WooCommerce Bookings: 1.15.31
• WooCommerce Product Vendors: 2.1.45

Additional context I have also added to this thread with a information, findings and debug https://github.com/wp-graphql/wp-graphql-woocommerce/issues/253#issuecomment-786905842

Hello, I would like to know how to apply the value of the "shipping metrod", it seems to me to receive only one String, how to insert a value together in the mutation checkout? thankss

'shippingMethod' => array (
'type' => 'String',
'description' => __ ('Order shipping method', 'wp-graphql-woocommerce'),

Your checklist for this pull request

Thanks for sending a pull request! Please make sure you click the link above to view the contribution guidelines, then fill out the blanks below.

🚨Please review the guidelines for contributing to this repository.

• [x] Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• [x] Make sure you are requesting to pull request from a topic/feature/bugfix branch (right side). Don't pull request from your master!

What does this implement/fix? Explain your changes.

Migrates to Travis-CI to Github Actions

Does this close any currently open issues?

…

Any relevant logs, error output, GraphiQL screenshots, etc?

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)

Any other comments?

…

Where has this been tested?

Operating System: Linux Mint 19.2

WordPress Version: 5.3.2

Your checklist for this pull request

Thanks for sending a pull request! Please make sure you click the link above to view the contribution guidelines, then fill out the blanks below.

🚨Please review the guidelines for contributing to this repository.

• [x] Make sure you are making a pull request against the develop branch (left side). Also you should start your branch off our develop.
• [x] Make sure you are requesting to pull request from a topic/feature/bugfix branch (right side). Don't pull request from your master!

What does this implement/fix? Explain your changes.

Adds supports for processing payments using the Stripe payment gateway and the checkout mutation.

• To do this the IDs of the Stripe Customer, Source, and Payment Intent objects connected to the future order must be provided as _stripe_customer_id, _stripe_source_id, and _stripe_intent_id to the metaData field in the CheckoutInput when executing the mutation.
• This only works with the Stripe payment gateway currently as far as I know, however other payment gateways may use WooCommerce order meta field to process order payments.
• If you need a explain of sorts you can view this test. The stripe/stripe-php library is used to execute the Stripe API requests and create the stripe objects. This process can also be in client-side in Javascript with the Stripe JavaScript libraries and it's encouraged.

Does this close any currently open issues?

…

Any relevant logs, error output, GraphiQL screenshots, etc?

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)

Any other comments?

…

Where has this been tested?

Operating System: Linux Mint 19.2

WordPress Version: 5.2.3

The relationship field in ACF establishes connections to other Post Types. Product is a Post Type, but WooGraphQL resolves Products differently than WPGraphQL resolves any other type of Post Type, so fields like this that expect a Post model to be returned don't get a Post model returned, but instead a Product.

To Reproduce

1. Have wp-graphql, wp-graphql-woocommerce, wp-graphql-acf and wp-graphiql installed.

2. Add an ACF Field group to posts, example field group export below: [ { "key": "group_5e85643c0cc84", "title": "Testing Product Relationship issue", "fields": [ { "key": "field_5e85644be0a13", "label": "Post Products", "name": "post_products", "type": "relationship", "instructions": "", "required": 0, "conditional_logic": 0, "wrapper": { "width": "", "class": "", "id": "" }, "show_in_graphql": 1, "post_type": [ "product" ], "taxonomy": "", "filters": [ "search", "post_type", "taxonomy" ], "elements": "", "min": "", "max": "", "return_format": "object" } ], "location": [ [ { "param": "post_type", "operator": "==", "value": "post" } ] ], "menu_order": 0, "position": "normal", "style": "default", "label_placement": "top", "instruction_placement": "label", "hide_on_screen": "", "active": true, "description": "", "show_in_graphql": 1, "graphql_field_name": "TestingProductRelationshipIssue" } ]

3. Run query in wp-graphiql. Sample query below: query SampleQuery { __typename posts(first: 10) { edges { node { title TestingProductRelationshipIssue { postProducts { ... on SimpleProduct { id name sku } } } } } } }

Expected behavior Should return results without errors

Screenshots https://slack-files.com/T3PDM1KRC-F0118V1GM0D-eab1d0676d

Additional context Slack message thread about the issue: https://wp-graphql.slack.com/archives/CCYJRDN4A/p1585794638031200

Hello Guys,

Thanks a lot for the great effort on this module.

I'm currently implementing an ecom in WooCommerce/Gatsby and found the wp-graphql project which is great.

But while trying to use it, in specific the WooCommerce project I have been pretty much guessing how I'm suppose to use it.

At the moment seems that I have understood well, but I have seen that documentation is definitely lacking.

I'm no PHP programmer, but wanted to offer a hand on improving documentation if that might work.

Describe the bug I am trying to use graphql_product_connection_query_args filter like this -

			add_filter( 'graphql_product_connection_query_args', function ( $query_args, $source, $args, $context, $info ) {
				
				if ( 'auction' !== $source->type ) {
				 	return $query_args;
				}

				$query_args['auction_arhive'] = true;
				$query_args['show_past_auctions'] = true;

				return $query_args;
			}, 10, 5 );

Using this code, $source is getting null. it should be a product object if I am not wrong.

Please suggest if I am missing something. Thanks

Plugin Versions

**WooGraphQL Version: 0.7.0 **WPGraphQL Version 1.1.3 **WordPress Version: 5.6.1 **WooCommerce Version: 4.9.2

Describe the bug For user authentication, I am using wp-graphql-jwt-authentication plugin. When trying to execute any mutation with an authorization header set, I get the error code 500 - internal server error. When trying to execute a query, I get results but with the error code 403. After looking at the server logs (see below) it seemed to originate from this plugin and not wp-graphql-jwt-authentication

To Reproduce Steps to reproduce the behavior:

1. Login using login mutation from wp-graphql-jwt-authentication
2. Use the received authToken in the header to execute any mutation

Expected behavior The mutation should get executed and return a result.

Error Log

PHP Fatal error: Uncaught GraphQL\Error\UserError: Woo session transaction executed out of order in [email protected]/wp-content/plugins/wp-graphql-woocommerce/includes/utils/class-session-transaction-manager.php:220
Stack trace:
#0 [email protected]/wp-includes/class-wp-hook.php(310): WPGraphQL\WooCommerce\Utils\Session_Transaction_Manager->pop_transaction_id(Object(GraphQL\Executor\ExecutionResult))
#1 [email protected]/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array)
#2 [email protected]/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#3 [email protected]/wp-content/plugins/wp-graphql/src/Router.php(536): do_action('graphql_process...', Object(GraphQL\Executor\ExecutionResult), Object(GraphQL\Executor\ExecutionResult), '', 'mutation AddToCart...', NULL, 403)
#4 [email protected]/wp-content/plugins/wp-graphql/src/Router.php(275): WPGraphQ in [email protected]/wp-content/plugins/wp-graphql-woocommerce/includes/utils/class-session-transaction-manager.php on line 220

Plugin Versions

• WooGraphQL Version: 0.12.0
• WPGraphQL Version: 1.13.7
• WordPress Version: 6.1.1
• WooCommerce Version: 7.2.2

Describe the bug

We have a problem in an online store using the WPGraphQL WooCommerce (WooGraphQL) plugin. It manifests itself in such a way when we want to add a product to the basket when we are logged in and authorized, we cannot do it because on the GraphQL and Wordpress side we get ERROR, which causes us to lose communication and the operation cannot be performed.

Error from debug.log: "PHP Fatal error: Uncaught GraphQL\Error\UserError: Woo session transaction executed out of order in /public_html/wp-content/plugins/wp-graphql-woocommerce-2/includes/utils/class-session-transaction-manager.php:220"

I edited the plugin and commented out this line in the plugin code. Then everything started working as it should.

Expected behavior

Operations performed via GraphQL and Apollo Client using the wp-graphql-woocommerce plugin should not lose connection due to an error. The code under the path /public_html/wp-content/plugins/wp-graphql-woocommerce-2/includes/utils/class-session-transaction-manager.php:220 breaks the connection and makes it impossible to perform other operations. Commenting out this solved the problem for me temporarily.

Plugin Versions and other

• WooGraphQL Version: 0.11.2
• WPGraphQL Version: 1.11.2
• WordPress Version: 6.1.1
• WooCommerce Version: 6.3.1
• Gatsby Version: 4.17.2
• GatsbySourceWordpress Version: 6.10.2
• React Version: 17.0.1
• Node Version: 14.17.0
• ApolloClient Version: 3.6.9

Additional context

Is this a bug? Is the problem elsewhere? I temporarily solved the problem by commenting out some plugin code but this is not an optimal solution and problematic if we want to update the plugin.

When I try to run the Order query passing an orderNumber as id

order(idType: ORDER_NUMBER, id: "123") {
    orderNumber
    orderKey
  }

I get an error: "No order ID was found corresponding to the order_number: 123"

If I pass an orderKey instead:

order(idType: ORDER_NUMBER, id: "wc_order_Zjd4Iusj4poZ") {
    orderNumber
    orderKey
  }

I get the wanted response:

{
    "order": {
      "orderNumber": "123",
      "orderKey": "wc_order_Zjd4Iusj4poZ"
    }
}

Looking at the code, I've found the step where this check is executed: https://github.com/wp-graphql/wp-graphql-woocommerce/blob/23c7f303479e0daa9516133c68ba9b523f5128fa/includes/type/object/class-root-query.php#L187-L190

To query by the orderNumber,this would have to change for a orderNumber "lookup".

If passing the orderKey is the expected behaviour, I suppose changing the idType to ORDER_KEY would avoid this confusion.

I have WPGraphQL Version 1.13.6 installed

I have activated the plugin WPGraphQL WooCommerce (WooGraphQL) ver 0.12.0 and getting this error message

WooGraphQL appears to have been installed without it's dependencies. It will not work properly until dependencies are installed. This likely means you have cloned WPGraphQL from Github and need to run the command composer install.