BigCommerce for WordPress Plugin Update Required!

We have deployed a fix for a recent vulnerability found with the BigCommerce for WordPress plugin.

To prevent security vulnerabilities, please upgrade your plugin by following the steps below.

1. Navigate to your WordPress website and log in as an admin.

2.  In the sidebar, select "Plugins".

3.  Select the "update now" hyperlink for the BigCommerce for WordPress plugin.

4.  Wait for the upgrade to finish.

We are implementing an internal migration for GET v3/catalog/categories and GET v3/catalog/categories/{category_id} endpoints to enhance our API’s performance. If you experience any unexpected API behavior on the following endpoint, please check the documentation to ensure all accurate query params and API usage.

These panels will now return up to 10 images per product, instead of returning all of the images on each product if there are greater than 10. This change will result in improvements to storefront performance when products on the store have a large number of images.

If the design of your storefront relies on accessing the data for a large number of images for each of these products, please consider using a GraphQL query instead to access more images. GraphQL can be used to fetch additional data as frontend API calls, or can be embedded in Frontmatter to be utilized directly within the theme context via Handlebars.

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.

For example, HTTP header names such as X-Rate-Limit-Requests-Left may instead be returned as x-rate-limit-requests-left. Per the HTTP specification (https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2), HTTP header names should always be treated as case-insensitive, so we do not consider this to be a breaking change to the API. Most HTTP clients already treat headers with the appropriate case insensitivity, so we expect minimal customer impact from this change.

No changes are being made to HTTP header values as part of this change.

As this bug was resulting in CLI requests incorrectly redirecting which resulted in a degradation of the local development experience, we have bumped the required version of CLI to 3.5.0to limit the customer impact of this issue. All CLI versions before 3.5.0 are affected. All users are strongly encouraged to update immediately in order to avoid issues during local development.

To get the latest version of stencil-CLI, simply run this command in your terminal:

npm install -g @bigcommerce/stencil-cli

On April 30, 2021, the Coupon API will limit the characters allowed in a coupon name. An error will result if any special characters other than the following are used in the Coupon code field:

• Alphanumeric values

• White spaces

• Underscores ( _ )

• Hyphens ( - )

To prevent a disruption in service, remove special characters from all coupon codes.