wbrubaker.a11n

output isn’t being properly unescaped

the order key is used in a few different ways – here’s a search result on the repo : https://github.com/woocommerce/woocommerce/search?q=order_key&unscoped_q=order_key

the order id will be unique within the site that the order was placed on.

Howdy ??

The checkbox coincides with the post status of the variation but as near as I can tell, that property is not supported by the REST API as it is not listed in the documentation here: https://woocommerce.github.io/woocommerce-rest-api-docs/#product-variation-properties

Which is another way to say that it appears to be working as designed.

I would suggest you report this on the github issue tracker for WooCommerce and see if support can be added for enabling/disabling product variations via the REST API. You can find the issue tracker here: https://github.com/woocommerce/woocommerce/issues

Hi there,

The arguments are not configurable. There is a filter named woocommerce_rest_orders_prepare_object_query which could be used to modify arguments if you would like to do that. There is an example of this filter being implemented here: https://github.com/woocommerce/woocommerce/blob/master/includes/api/class-wc-rest-network-orders-controller.php#L144-L151

the error is accurate as WooCommerce does not provide a method called post.

If you are trying to send a POST request via PHP code, you will probably want to look into the WordPress provided methods for that. The wp_remote_request helper function seems most appropriate – see the documentation for that here: https://developer.www.ads-software.com/reference/functions/wp_remote_request/

Sounds to me like the product type is not set to ‘variable’ and possibly the attributes aren’t set to be used for variations. I suspect that manually creating a variable product in accordance with the documentation here: https://docs.woocommerce.com/document/variable-product/ will yield expected results which would, in turn, answer your question about whether or not this is a WooCommerce issue.

Yes, that is possible. See the documentation here https://docs.woocommerce.com/document/managing-orders/#section-2

You might want to look into multisite for that https://codex.www.ads-software.com/Create_A_Network

I was able to submit the checkout form and was redirected to PayPal – the order id is 1956.

If you continue to have problems, I would suggest taking conflict resolution steps, i.e. Temporarily switch back to a default WordPress theme such as WordPress Twenty Seventeen Theme (https://www.ads-software.com/themes/twentyseventeen/) or Storefront (https://www.ads-software.com/themes/storefront/) and disable all plugins except for WooCommerce. If that resolves the issue, then re-enable features one-by-one until you find the one that’s causing the conflict.

There’s an index.html file that resides in the root folder where your WordPress installation lives (https://yagaschiliquest.com/index.html). This shouldn’t be there. What is happening, is that when the checkout process is making an AJAX call to wcajax=checkout that index page is loading instead. Since the AJAX call expects JSON as a response, but it is getting HTML instead so the error is presented: https://cld.wthms.co/FjktAq

You might want to look into something like the WooCommerce Product Vendors extension https://woocommerce.com/products/product-vendors/ but, there is no way to present payment options based on who the vendor is. The product vendors extension would use the same payment methods as are defined for the shop but vendors then get a portion of the sale and the store owner gets a portion.

If the JavaScript were enqueued using the same handle (see https://developer.www.ads-software.com/reference/functions/wp_enqueue_script/) it would only load the library one time. The handles used by WooCommerce are photoswipe and photoswipe-ui-default – if the theme uses those same handles to load the library, it would only be loaded once.