This article documents how to use widget versioning to update a widget template without updating its widgets.
access_token with content modify scope.This tutorial uses Cornerstone theme.
To create a widget template, send a POST request to v3/content/widget-templates.
Make a note of uuid and current_version_uuid. We will use them in the steps that follow.
You can use Page Builder, BigCommerce’s storefront editing and customization tool, to view your widget template in the control panel. It will be displayed in the left pane under Custom.
In this tutorial, you will create and place a widget programmatically. To place your widget using Page Builder, drag and drop the widget template from the left pane onto the page.
To create a widget using the Widgets API, send a POST request to /v3/content/widgets. Replace the widget_template_uuid placeholder with the uuid from the previous step.
Look for version_uuid and current_version_uuid in the response. The widget’s version_uuidshould match the current_version_uuid of the widget template.
You can place the widget on the storefront by creating a placement. The following example uses the home_below_featured_products region. To get a list of all available regions, send a GET request to v3/content/regions.
To place your widget, send a POST request to /v3/content/placements.
The widget should now be visible on your store’s homepage under Featured Products.
The create_new_version parameter controls whether widget updates are forced or opt-in. Omitting the create_new_version parameter or setting it to false will make it a forced update.
To create a new version of the widget template without affecting existing widgets, set create_new_version to true when sending a PUT request to /v3/content/widget-templates/{uuid}. This will create a new widget template version record and associate that record to the current_version_uuid.
Send a GET request to /v3/content/widgets/{uuid} to retrieve your widget’s data.
You will notice that current_version_uuid has changed and is now different from the widget’s version_uuid. Although you have updated the widget template, the widget created using that template did not change.
All widgets created after the update will be based on the most current version. Let’s create another widget to test this functionality.
Send a POST request to /v3/content/widgets replacing the widget_template_uuid placeholder with your widget template uuid.
To display the new widget next to the old one, place it in the same region. In our case, it is home_below_featured_products.
You should now see two different widgets displayed below Featured Products.
To upgrade the widget derived from the original widget template, send "upgrade":true in a PUT request to /v3/content/widgets/{uuid}. This will push the widget up to the latest widget template version.
If the newer version of your widget template contains different schema settings, you need to provide the necessary configuration values along with the upgrade flag to make sure the widget is updated correctly.