November 4, 2024- Commerce 3.6.3 (Beta)
Beta Release Date: 11/4/24
Commerce 3.6.3 Release Notes |
---|
Resolved Issues
Dynamic Pricing Season Requirement
In version 3.6, we introduced a requirement to assign a season to all products configured with dynamic pricing. This update improves data integrity and enhances pricing reliability.
With this release, we have also resolved several bugs related to dynamic pricing, reinforcing the importance of season assignments. During upgrades, a data fix will automatically:
Assign a generic season to any dynamically priced products missing one.
Ensure all override windows are set to track quantity.
Set a default quantity of 10,000 for any pricing entries missing a specified quantity.
These adjustments help ensure accurate pricing and availability for affected products.
NOTE: Our dynamic pricing documentation has been updated to reflect that assigning a season is now a prerequisite for dynamic pricing configuration. Use Dynamic Pricing Version 1 only for removing or modifying prices for specific dates, while Dynamic Pricing Version 2 should be used for initial dynamic pricing setup.
reCAPTCHA with Cloud UI PDP
We have resolved a reCAPTCHA issue affecting resorts on Cloud UI that was introduced in version 3.4.1. With this release, reCAPTCHA is now functioning correctly across most areas, with the exception of modals on Cloud UI PDPs for the following configurations:
Voucher module
Add Group Member module
Please note that both the Voucher and Add Group Member modules work as expected in My Account, in checkout, and on standalone pages.
Important: If you do not take this release and are on Cloud UI, you must turn off reCAPTCHA or the modules below will continue to fail even if unchecked.
For resorts on Cloud using these modules on any PDP without "Use Legacy Product Page" selected, we recommend disabling the following reCAPTCHA settings:
Go to Admin > Settings > General Settings > ReCaptcha
Uncheck Enable on add family member modules
Uncheck Enable on vouchers module
Complex Order Failure in Order Queue
We resolved an issue that caused large orders with many attributes to fail in the order queue for resorts on version 3.5 or earlier, or to continuously retry without fully processing for those on version 3.6 or later. With this release, these complex orders should now process smoothly.
Please note that after this update, your Customer Success Specialist will work with you to determine the desired status for any orders currently in this state. For instance, an order already rebuilt in RTP can be set to “success,” while a recent order that hasn’t yet processed may be set to “ready” to reprocess with the upgrade.