...
For customers using Payeezy as a gateway, if configured for AVS and CVV, this failure/pass message is now being sent with the pre-auth as well as the tokenized call.
For resorts using the Heartland Payment Gateway, the “Sandbox mode” messaging persists when production credentials were added. This can be temporarily fixed in 2.22 versions using an HTML Widget. Talk to your Aspenware representative if this is desired.
For resorts using Aspenware Payment Plans, on very few payment plan payments when a certain error is returned, the customer is successfully charged more than once but shows as failed payment in Aspenware Commerce.
The RemoveDeletedInventory function was optimized.
Some Admin roles could not see Release Version information from within the Aspenware Commerce Administration Dashboard, this has been resolved.
For products that are set up to use Radio-button date functionality (such as camps, events, seasonal programs, etc.) cutoff windows were not being properly enforced. This issue is resolved.
For resorts using the Arrive Parking integration, when a customer navigates to a future month in the date selector for Arrive products, no inventory is available. If they navigate forward, then back to the future month that did not display dates, dates will become available.
For resorts using the Arrive Parking integration and Authorize.net, if a customer had a credit card failure message while booking a parking product, the parking booking would succeed on initial confirm attempt rather than on order complete success, occasionally resulting in double parking bookings. Now, if a credit card charge failure occurs on the confirm step, the attempted booking is canceled (though the customer will be emailed that it’s canceled) and the parking booking will only persist if an order is successfully completed.
Retail Product Detail Page Images were not displayed on desktop for some themes.
Some resorts have reported that the order history page “bleeds off the page” and this appears to be theme specific and will be handled case by case. If you notice your site experiencing this, contact support@aspenware.com. This has been fixed for a number of resorts in 2.23.
...
Known Issues
| Note |
|---|
IMPORTANT: If you sell a $0 resort charge product to enable resort charge or direct to lift capabilities in RTP|One, do not take this release. A hotfix is expected to be fixed in 2.23.1 (expected to be cut the week of 11/15) |
For resorts using Heartland as a payment provider, if an order total is $0, due to a free product or customer using alternate payment methods to pay off the balance of their order, and the order has a resort charge product, the token stored in RTP|One is not a multi-use token that can be used onsite. This is expected to be fixed in 2.23.24 (mid-Dec minor release1 (a hotfix that will be cut the week of 11/15)
For resorts using Payeezy or Authorize.net as a payment provider, if an order total is $0, due to a free product or customer using alternate payment methods to pay off the balance of their order, and the order has a resort charge product, the primary credit card profile in RTP|One is not created. This is expected to be fixed in 2.23.1 (a hotfix that will be cut the week of 11/15)
For resorts using Payeezy, Authorize.net, or Heartland, if a resort charge product is for sold for $0, orders with this $0 resort charge product will receive an error in checkout and will not be able to be processed. This is expected to be fixed in 2.23.24 (mid-Dec minor release1 (a hotfix that will be cut the week of 11/15)
For resorts using Payeezy as a payment provider, if an order total is $0, due to a free product or customer using alternate payment methods to pay off the balance of their order, and the order had a resort charge product, the primary credit card profile is not getting properly stored in RTP|One. This is expected to be fixed in 2.24 (mid-Dec minor release)
When entering a media id on a Fast Flow product, when selecting enter key instead of clicking validate, Enter key refreshes the page. This is expected to be fixed in 2.24 (mid-Dec minor release)
Some failures to send orders to the POS occur during very high volume periods when a timeout happens on the order complete page and a customer clicks Confirm a second time after the initial time out. This is expected to be fixed in 2.25 (early-Jan major release)
For resorts using the Arrive Parking integration and Authorize.net, if a customer has more than one credit card failure message while booking a parking product, the parking booking will succeed on the second confirm attempt rather than on order complete success, occasionally resulting in double parking bookings. This is expected to be fixed in 2.25 (early-Jan major release)
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. This is expected to be fixed in 2.24 (mid-Dec minor release)
For resorts using Unity and Retail functionality, a shipping fee product should be sold into RTP when an order-level shipping charge is added to an order. Presently, this additional shipping fee product is not included in the order when it gets to RTP|One. This is expected to be fixed in 2.24 (mid-Dec minor release)
For resorts that use Print at Home Ticketing functionality, when a customer purchases different days within the same order, the print at home follow-up email, which contains the barcodes, lists the first product date for each barcode in the email, and the subsequent dates are not listed. The QR codes themselves are correct and the products were sold for the correct dates, however, the date right next to the QR codes shows incorrectly. This is expected to be fixed in 2.24 (mid-Dec minor release)
Aspenware recommends using product cutoff days to automatically direct guests to the first month of the season on the pricing calendar, however, there isan 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.
Aspenware Identity doesn’t automatically redirect the guest back to the PDP they were on prior to selecting to sign in unless they explicitly use a redirect URL where sign-in is required. This is a feature enhancement to Identity.
Guests who do not have a birth date defined on their profile are not able to log in through Identity.
Though a requested field for the rental profile, shoe size is not required and can be
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.
My Account- print vouchers will print the entire screen, not just the voucher.
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, not just from Voucher Tools.
When using the Reimagined Dynamic Pricing modal to set prices for more than one season, ensure that you save the price for one season’s set of pricing, then open and close the modal to add prices for another season - otherwise initial pricing for the first season may be overwritten by the other season’s pricing.
For several resorts 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.
...