2.29 Commerce Release Notes

Owned by Leigh Bush, created
Last updated: Jan 05, 2024 by Sarah Holst
3 min read

With great pleasure, Aspenware presents Aspenware Commerce 2.29.
Release Date: May 23rd, 2022

New Features

reCAPTCHA v3 for Aspenware Commerce

Aspenware Commerce has now integrated reCAPTCHA v3 to keep your site more secure than ever. Unlike previous versions, reCAPTCHA v3 operates behind the scenes, without requiring user interaction. reCAPTCHA v3 can detect abusive traffic and challenge suspicious activity. Aspenware has added this configurable feature to several interaction points at risk for abuse by bots. For more information about reCAPTCHA v3 watch this short video, or see the reCAPTCHA v3 documentation to get started. The reCAPTCHA v3 feature is also available for Identity.

Upgrades

Square SDK Upgrade

Square has been upgraded to the latest Web Payments SDK including a modern web styling and updated security. For Square customers, any release after Aspenware Commerce 2.28 will include this latest integration as the SqPaymentForm library is deprecated as of May 13, 2021, and will only receive critical security updates until it is retired. See the Square SDK Upgrade Configuration Guide for any changes that may be made during your upgrade.

NOTE: Because a new Square payment token may be required, this upgrade may require some downtime.

Enhancements/Resolved Issues

Resolved Issues

  • Payment Plans - Removed the “Hotlist until paid” checkbox from Product Assignments.

  • Payment Plans - Resolved the issue when a payment plan enrollment was not being created for any products that were processed after a $0 payment plan was processed in the same order.

  • Date Picker - Resolved the issue where the date picker was displaying Russian characters sometimes.

  • Square/Payment Plans - When a resort is using multiple locations, the default location was not getting set correctly.

Known Issues

  • For resorts using the Arrive Parking integration and Siriusware as a POS, orders with Arrive Parking products will show as failed in the order queue.

  • Aspenware recommends using product cutoff days to automatically direct guests to the first month of the season on the pricing calendar, however, there is an issue where if the proper deep link was used, the correct default month will not load until the page is refreshed.

  • On the calendar on the product detail page (PDP), dates that are not defined with inventory in the POS are shown as sold out rather than crossed out. This is resolved on the large calendar, but not for the small PDP calendar.

  • Phone prefix is not being sent to RTP|One when the phone number is collected in checkout.

  • When a phone number is updated in My Account, it is resulting in an invalid number being added to the beginning of the phone number in RTP|One.

  • Guests who do not have a birth date defined on their profile are not able to log in through Identity. This will be tracked in Identity release notes going forward.

  • A customer is able to checkout with a product if the store cutoff time expires but the product is already in the cart. A similar issue was fixed in 2.15, however, this resolved issue was focused on the specification attribute for cutoff days, not time.

  • If certain words are used in attribute descriptions, such as “days”, “date”, “day” that are not Start Date or Number of Days attributes, it can impact whether age rules work on the product. See this doc for common troubleshooting.

  • The query that runs to display vouchers for the My Account page is only checking if the vouchers were created from a transaction in RTP|One, not just from Voucher Tools.

  • When using the Reimagined Dynamic Pricing modal to set prices for more than one time period, ensure that you save the price for one time period’s set of pricing, then open and close the modal to add prices for another time period - otherwise initial pricing for the first season may be overwritten by the other time periods’ pricing.

  • For several resort themes, strong and bold HTML tags are no longer working for short and long descriptions.

  • For resorts that use the SheerID integration, products that require SheerID validation must have either a waiver, child reg profile, rental profile, or prompt added to them in order to display the necessary SheerID checks. The fix for this would enable the personalization step to load and request the SheerID validation without anything else configured on the product that requires personalization.

  • Currently, in resort environments using Square for payment processing, credit cards that don’t require postal codes during checkout or in My Account and International credit cards are not processing correctly.