On April 15, 2022, the behavior of the product.images node in the GraphQL storefront API will be changing to only return 10 images by default. If you wish to request a different number of product images, you should specify the `first` argument explicitly with your request, which is considered a best practice when interacting with any paginated collection.

For example, if you were previously sending a request like this:

query productsWithImages {
   site {
     products {
       edges {
         cursor
         node {
           entityId
           name
          images { // will return 10 images unless explicit arguments are specified
            edges {
              node {
                url(width: 640)
              }
            }
          }
         }
       }
     }
   }
 }

You could instead send a request like this:

query productsWithImages {
   site {
     products(first: 5) { // as a best practice, use `first` on all collections to specify page size
       edges {
         cursor
         node {
           entityId
           name
          images (first:20) { // will return up to 20 images per product
            edges {
              node {
                url(width: 640)
              }
            }
          }
         }
       }
     }
   }
 }

Please note that requesting larger amounts of data with increased page sizes will factor into the GraphQL complexity calculation for your query.

WordPress

• Added documentation that outlines how to improve WP-Cron reliability when using the BigCommerce for WordPress plugin.

Developer Blog

• V3 Pages API Debuts Bulk Operations & MSF Compatibility

API

• Added support to allow the gift wrapping option to be managed via Server-to-Server Cart API.

• Added Create a Customer Address and Update a Customer address endpoints to resolve duplication behavior for customer addresses in the Customer v3 API.

• Added visibility to new refund override fields in the Create a Refund and the Get Refunds for Order endpoints.

Checkout

• Added documentation describing how to create and update a consignment using the Checkout Consignment API.

Webhooks

• Added the ability for the store/customer/updated webhook to trigger when the account signup custom form fields is updated.

Theme

6.3.0

• Update blog component to use H1 tags on posts. #2179

• Remove Compare Form. #2162

• Fixed password complexity error not displaying the complexity rules set in the store settings. #2117

• Translation updates February 2022. #2177

• Cornerstone performance optimizations: blocking scripts delaying DomContentLoaded. #2158

• Cornerstone performance optimizations: remove unused fonts. #2176

• Update stencil-utils package. #2157

• Add google recaptcha to the password reset request page. #2164

Customizing Checkout

• Added support for Installing a Custom Order Confirmation Page

4.25.0

View release 4.25.0 on GitHub

Added

• Added ability to control images import. It adds the ability to choose between serving images from external CDN, skip import completely, or serving images as usual. To access these settings go to Bigcommerce > Settings > Product Sync > Images Import. There are three options to choose from:

  • Full images import - the default behavior. During the sync with BigCommerce, each image is downloaded and stored in WordPress locally. All images are served from the WordPress environment

  • Import only images URL - a new option that allows you to only retrieve images URIs from BigCommerce and serve images with that URIs. Images won't be stored in WordPress locally and will be loaded from an external source(Bigcommerce CDN)

  • Disable images import - completely disable images import. No images are added to the WordPress environment during the sync process. Images from Bigcommerce CDN won't be loaded either. However, you are still able to set a featured image on the product and it will be displayed on the frontend

API

The Pages v3 API now offers bulk create and bulk update operations.

Developer Blog

What’s New for Merchants in February?

API

Added new endpoint:

• Update Customer Messages

Added new limits:

• Checkout V3 - 50 character limit for coupon codes

• Marketing V2 - 250 character limit for messages

• Orders V2 - 65535 character limit for order shipment comments

• Orders V3 - 50 metafield limit per order

• Checkout Storefront - 2000 character limit for messages

Added new response codes:

• 207 status to Create a Page and Update a Page

• 409 status to Update a Channel

Stencil

• Added the ability to apply one theme to multiple storefronts/channels. See Stencil CLI Options and Commands for the available options.

• Added support for Spanish (Mexico) for the checkout’s supported translation keys.

Developer Blog

• Employee Spotlight: Chris Sean

• BigCommerce Employee Spotlight: Katie Hoesley

4.24.0

View release 4.24.0 on GitHub

Added

• Added separate logging section for webhooks. The section can be found under Settings -> Diagnostics -> Get Diagnostics. It shows entries from webhooks incoming requests(validation issues, endpoints triggering, webhooks errors)

Fixed

• Fixed the customer's cache purging during the final import cleanup. Cache cleanup was moved to a background cron job to prevent the import process freeze due to the store's high number of customers.

• To speed up the import process running import tasks in parallel was added. You can enable the option in BigCommerce > Settings > Product Sync. Enabling it will add an additional background task runs on listings, channels initialization, and product data fetching.

• Added support for customer webhooks, which will enable real-time data syncing between BigCommerce and BC4WP for customer-related data, such as new customers being created and updated login settings. You can enable the option during the onboarding process or in BigCommerce > Settings > Product Sync.

We are excited to announce the beta launch of the new BigCommerce Dev Center!

Our Vision
Your feedback is truly at the heart of this change. Over the past year, our developer advocates, product & engineering teams, and support agents have heard you loud and clear. Developers building with BigCommerce want better ways to get the answers and information they need. We took your feedback, explored the pain points, and made changes to improve the dev docs experience.

Our goal is to make it easy for you to find the documentation, resources, and tools you need to get started building quickly and have your questions answered promptly. We wanted to make the experience of using our dev docs simpler, more streamlined, and more rewarding. And we’re just getting started! 

The new site lays the groundwork for the enriched developer experience and expanded resources we’re excited to introduce over the coming months. We want to empower you to design BigCommerce solutions that meet your needs and exceed your expectations, to engage with us as we create new content, and to know that you’re never working on BigCommerce products alone.

What’s Next?
During this beta phase, the current site at developer.bigcommerce.com will remain live. However, we encourage you to use the new Dev Center at developer-beta.bigcommerce.com and provide feedback to our team. We’ll be actively publishing and updating content on the beta site, making it the most up-to-date source for docs and resources moving forward.

Have questions or feedback? Fill out a feedback form here. We look forward to hearing from you!