2020.1.x Minor Releases

Refer to the following minor release notes for the latest updates to SuiteCommerce, SuiteCommerce MyAccount, and SuiteCommerce Advanced:

2020.1.12 Release of SuiteCommerce and SuiteCommerce Advanced

Fixes

  • Issue preventing the Order Received notification email from being sent when customers choose Pick Up In Store during checkout.

  • Issue preventing customers from selecting payment methods that support 3D Secure 2.0. Merchants can now communicate payment gateway challenges using Window.postMessage().

2020.1.11.1 Release of SuiteCommerce and SuiteCommerce Advanced

Fixes

  • Issue causing "Please select a credit card" error message to display instead of the Review Your Order page when shoppers click the Back button on the Checkout page. This issue was isolated to web sites configured for One Page Checkout and shoppers with terms included on their customer records.

  • Issue preventing auto-population of credit card street and zip code information on the Billing tab for a Sales order due to AVS Street Match and AVS Zip match failing with an "Unsupported by processor" error. This issue was isolated to sites where the Payment Instruments feature was enabled for payment processing.

2020.1.10 Release of SuiteCommerce and SuiteCommerce Advanced

Fixes

  • Issues when clicking I want to ship to multiple addresses using one-page checkout. This issue resulted in blank shipping and delivery method sections, relying on the shopper to click Continue to redirect to the correct flow.

2020.1.9 Release of SuiteCommerce and SuiteCommerce Advanced

Fixes

  • Issue creating two Item Search API calls for relateditems_details and correlateditems_details.

  • Issue causing the Cart to sort items by Internal ID, not according to sequence when added to the Cart, as expected.

  • Issue preventing matrix item images from zooming on mouse over.

  • Issue causing a shopper’s Purchase History to display a purchased quantity of 1, regardless of the actual quantity ordered.

2020.1.8 Release of SuiteCommerce and SuiteCommerce Advanced

Fixes

  • Issue preventing users from sorting product reviews with multiple pages.

  • Issue preventing credit card authentication process during checkout on websites with 3D Secure 2.0 enabled.

  • Issue triggering an incorrect Google Tag Manager SearchItem-end event.

  • Issue preventing special characters from being used in the phone number field.

2020.1.7 Release of SuiteCommerce and SuiteCommerce Advanced

Fixes

  • Issue causing the shipping method to continuously reload after a user edits one of its fields during guest checkout.

  • Issue where enabling the Same as shipping address option during checkout causes removal of the name provided for the shipping address and failure to populate the billing address fields. This behavior was isolated to users logged in as Company customers.

2020.1.6 Release of SuiteCommerce and SuiteCommerce Advanced

Fixes

  • Issue causing customer credit card information to be saved for open invoices paid from the My Account > Billing page when the Save Credit Card Info by Default preference is disabled.

  • Currency conversion issue causing the total amount of a customer’s return authorization to be less than the amount from the original sales order.

  • Issue preventing mobile users from accessing the Save for Later page from their shopping cart.

2020.1.5 Release of SuiteCommerce and SuiteCommerce Advanced

Fixes

  • Issue preventing users from removing, selecting, or adding a shipping address during checkout on sites configured for One-Page checkout flow.

  • Issue preventing multi-language sites from displaying the correct language on the Phone Number entry validation message. For example, a multi-language site properly configured for Japanese incorrectly displays, Phone is required, in English.

  • Issue preventing users from setting a default credit card on sites implementing the payment instruments feature.

2020.1.4 Release of SuiteCommerce and SuiteCommerce Advanced

Security

In the 2020.1.2 release of SuiteCommerce and SuiteCommerce Advanced, a new Security subtab was added to the Advanced tab of the Configuration Record. The Security subtab provides settings to control whether your site's pages can be rendered in a frame. For more information, see Security Subtab. The default setting, which disallows framing by all domains other than your own, is now active. You should change the default if you want to continue to allow other domains to render pages in a frame.

Improvements

  • Updated the jQuery JavaScript library to version 3.5.1.

  • Added an Enable Zoom for Images option to the Shopping Catalog Tab of the Configuration Record. This new option is enabled by default so that images in the Product Details Page and Quick View display at zoom size when a user hovers over them. For more information, see Shopping Catalog Tab.

Fixes

  • Updated SuiteCommerce and SuiteCommerce Advanced to ensure HTTP security headers are included in all SuiteCommerce and SuiteCommerce Advanced sites.

  • Issue causing the error message, Please Provide a Billing Address, to be displayed to customers who have provided a billing address during checkout in the One Page Checkout and Billing First flows.

  • Issue causing images that include a zoom size in the image resizing options to resize when a user hovers over them.

  • Issue that allows customers with Quote permissions to place an order and complete the checkout flow from the Quote Detail Page without selecting a billing address.

  • Issue preventing changes made to custom skins using the SMT Theme Skin Manager from being saved.

  • Issue preventing customers from removing previously entered zip codes in the Estimate Tax and Shipping field during checkout.

  • Issue causing all associated images for a selected item to display at the same time on the Product Details Page or in the Quick View.

  • Extension Manager issue causing Font Awesome icons to display as question marks on sites that do not use UTF-8 character encoding.

2020.1.3 Release of SuiteCommerce and SuiteCommerce Advanced

Fixes

  • Issue resulting in a blank My Account page for customers with more than 1000 invoices. As a result, you may see an error in the console such as: Uncaught SyntaxError: Unexpected token '<' on MyAccountEnvironment.Service.ssp.

  • Issue preventing multiple image scrolling on a product’s details page after launching a modal window, such as might occur after clicking the Add to Cart button.

  • Product reviews issue resulting in no feedback or acknowledgement after the shopper selects yes or no when asked Was this review helpful?. As a result, you may see an error in the console such as: jQuery.Deferred exception: Cannot set property 'innerText' of undefined TypeError: Cannot set property 'innerText' of undefined.

  • Issue resulting in an incorrect message to the shopper. In this case, a shopper adding an item quantity that is unavailable receives a message alerting them to reduce their order and click a link. This issue displayed a URL for the link instead of text.

  • Issue preventing shoppers from accessing or editing payment methods when checking out (on webstores set up for one-page checkout) or when editing settings in My Account.

  • Issue customizing the LoginRegister.Register.View module using the Extension Developer Tools. Implementing the addToViewContextDefinition method results in the following error: INVALID_PARAM: The specified view_id ('LoginRegister.Register.View') is not valid for the current component or the callback is not a function.

2020.1.2 Release of SuiteCommerce and SuiteCommerce Advanced

Security

A new Security subtab has been added to the Advanced tab of the Configuration Record. The Security subtab provides settings to control whether your site's pages can be rendered in a frame. For more information, see Security Subtab. The default setting disallows framing by all domains other than your own, so you need to change the default if you want to continue to allow other domains to render pages in a frame. The default setting is not yet active to ensure you have time to change it if needed. Monitor future release notes to learn when the new default setting is activated.

Fixes:

  • Issue causing customers who try to place an order from a Quote Detail page to be redirected to the Thank You page instead of the External Payment page.

  • Issue where enabling the Payment Instruments feature for your company causes blank pages to be displayed for users who try to access the My Account and Checkout pages.

  • Issue preventing cash sales made via SuiteCommerce InStore from displaying in Purchase History for My Account.

  • Issue preventing the cartView event being triggered on the Cart page in the Google Tag Manager data layer when using the Criteo service.

  • Issue causing product images to move to the left when viewing successive images using the zoom feature.

2020.1.1.1 Release of SuiteCommerce and SuiteCommerce Advanced

Fixes:

  • The OrderHistory and ReturnAuthorization modules have been rolled back to SuiteScript 1.0. Migration of these modules to SuiteScript 2.0 in SuiteCommerce/SuiteCommerce Advanced release 2020.1.0 caused unexpected issues with field sets.

  • Issue with instrumentation module negatively impacting SEO page generator.

2020.1.1 Release of SuiteCommerce and SuiteCommerce Advanced

Fixes:

  • Issue preventing the quantity number for an order displayed in My Account > Purchase History from matching the original quantity number.

  • Issue causing a missing Product Internal ID in the data layer communicating to Google Tag Manager on product-related events, such as productList and productView.

  • Issue involving http 301 responses (permanent URL redirection) resulting in the following error: ERR_TOO_MANY_REDIRECTS. This occurred when the URL for an item contained multiple URL fragments.

  • Issue causing external payment methods to fail, resulting in the following message: Payment method is not supported for this gateway.

  • Issue preventing pending or partially paid invoices from displaying in the Invoices menu of My Account.

  • One-page checkout issue resulting in both the shipping and billing addresses defaulting to one address after shoppers enter two separate addresses (Same as Shipping option remains unchecked).

  • SEO issue caused by exceeding the browser's localStorage capacity, resulting in the following error: QuotaExceededError: DOM Exception 22: An attempt was made to add something to storage that exceeded the quota. This error occurred on secure domains with CDN enabled.

General Notices