You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, WP Gatsby does not support updates from WooCommerce. As products are updated, the incremental build feature should detect the content changes, invalidate the cache for the updated product, and build the page and any other uses of the product throughout the site.
At least the following updates should be possible for both wpSimpleProduct, and wpVariableProduct, bonus if wpBundleProduct can be supported:
name (similar to title for blog posts and pages), id, databaseId, slug.
Content sections of a WooCommerce product, including the main content and shortDescription queries.
SEO changes.
ACF fields attached the the product.
Images, including the featured image and galleryImages.
Inventory status, including stockQuantity, stockStatus, backorders (allowed or not)
Type (simpleProduct, variableProduct, etc.)
Shippng information, such as weight, length, width, height.
Many of these are added and updated through the admin section of WooCommerce, but it's also important to support changes made when products are purchased, orders are canceled or refunded, and other action hooks in WooCommerce that effect the items above.
At the moment, we query for the following via WooGraphQL:
WooGraphQL is currently making globalAttributes available as a query, fixing a bug that previously prevented them from being used. When these are available, changes to them and the way they effect individual products.
At the moment, WP Gatsby does not support updates from WooCommerce. As products are updated, the incremental build feature should detect the content changes, invalidate the cache for the updated product, and build the page and any other uses of the product throughout the site.
At least the following updates should be possible for both
wpSimpleProduct
, andwpVariableProduct
, bonus ifwpBundleProduct
can be supported:name
(similar to title for blog posts and pages),id
,databaseId
,slug
.content
andshortDescription
queries.image
andgalleryImages
.price
,onSale
,regularPrice
,dateOnSaleTo
,dateOnSaleFrom
.stockQuantity
,stockStatus
,backorders
(allowed or not)weight
,length
,width
,height
.Many of these are added and updated through the admin section of WooCommerce, but it's also important to support changes made when products are purchased, orders are canceled or refunded, and other action hooks in WooCommerce that effect the items above.
At the moment, we query for the following via WooGraphQL:
Our fragment queries for SimpleProducts are as follows:
For
variableProducts
, we use the following fragement:WooGraphQL is currently making globalAttributes available as a query, fixing a bug that previously prevented them from being used. When these are available, changes to them and the way they effect individual products.
As I understand it, most of these fields should be available by adding a Monitor to the WooCommerce
save_post
hook, such as the ones used in this file: https://github.com/gatsbyjs/wp-gatsby/blob/master/src/ActionMonitor/Monitors/Monitor.phpThanks,
Craig
The text was updated successfully, but these errors were encountered: