Beta Release Date: 10/11/2024
Release Date: TBD
Current Releases (as of 7/24/24) | ||||||
---|---|---|---|---|---|---|
Cloud UI | Commerce | Identity (Auth0) | Identity (Legacy) | Unity | Arrival | Resort Tools |
Commerce 3.6.1Currently in Beta Testing |
---|
Resolved Issues
Fixed issue where sticky add to cart was not properly enabling on legacy PDPs despite having the setting to enable this feature turned on.
Fixed an issue where product tile shadows on the PLP were cut off along the outer edges of the cards.
Aspenware Commerce now supports alphanumeric voucher formats, following an RTP update that enabled alphanumeric vouchers. Previously, vouchers could only be numeric. Although alphanumeric vouchers were accepted, they weren't invalidated properly if not entered in all caps, leading to overuse. This issue has now been corrected.
For categories that displayed golf tee time products for booking only, the display order now respects the display order defined in Aspenware Commerce admin.
Product descriptions for golf products, which previously restricted all HTML, have been updated to allow anchor tags. This enables links to external platforms, such as Noteefy, a tee time waitlist product, to be included in golf course tee time descriptions.
Please note: these links should be set to open in a new tab. Additionally, if HTML beyond anchor tags is added, it may disrupt the layout.
need to update golf docs - How to handle this in beta
For some devices, the floating action button (FAB) icon for loyalty program sign-up (for logged-out users) and points accumulation (for logged-in users) was hidden behind other elements, making it difficult to see. Additionally, the loyalty logo image appeared blank on certain devices. These issues have now been resolved.
Deploys for resorts that want this fix will need to be done by DevOps - but only the first deploy - due to infrastructure changes
Aspenware has fixed an issue in which resorts using the SendGrid email delivery system would see duplicate emails when sending bulk emails. Note: Due to infrastructure changes, resorts using SendGrid who take this release (or a later release that includes this change for the first time), will require DevOps resources for the upgrade.
Aspenware has added a fun enhancement to the media step in checkout. Now, customers can configure the text beneath the Add New Media and Reload Media text on the media card selection modal. Until a resort opts to change the language strings, the pre-existing hardcoded text will be the default language string (see below). While Aspenware recommends limiting text in this field, there is not character limit on the language string.
New Language String | New Language String Default |
---|---|
account.login.checkout.media.subhead.addmedia | Media Card(s) will be added to your order |
account.login.checkout.media.subhead.reload | Reload existing Media Card(s) |
NEED TO REVISE THIS - PUR-3694
New language strings
Admin.Catalog.Products.ProductAttributes.AttributeCombinations.Fields.OverrideAttributeDescription
Admin.Catalog.Products.ProductAttributes.AttributeCombinations.Fields.OverrideAttributeTitle
Product-Level Attribute Titles and Descriptions Customization
Admins now have the option to define unique guest-facing titles and descriptions for attributes at the product level, streamlining attribute management across products. This provides greater flexibility and allows admins to offer clearer guidance to guests on the selections they can or should make on the product detail page (PDP).
Key Improvements:
A new collapsible section, Product Attribute Overrides, has been added to the product editor screen in admin. This allows admins to define product-specific attribute titles and descriptions.
The new Attribute Display section includes a grid of all attributes assigned to a product (including add-on attributes), displaying the global titles and descriptions, which are view-only.
Admins can now edit and save custom attribute titles and descriptions for each product.
Titles must be plain text.
Descriptions can include links (anchor tags) but no other HTML.
Both are optional, and if left blank, global values will be used instead.
Character limits from the attribute editor (200 characters) are enforced for product-specific configurations.
Invalid inputs trigger an error message, preventing incorrect data from being saved.
If no product-level title is defined, the system defaults to the attribute name on the front end.
New Language Strings Added:
"Attribute Display" (section title) - Need to get from Derrick Brown
"Override Attribute Title" (column header) - Admin.Catalog.Products.ProductAttributes.AttributeCombinations.Fields.OverrideAttributeTitle
"Override Attribute Description" (column header) - Admin.Catalog.Products.ProductAttributes.AttributeCombinations.Fields.OverrideAttributeDescription
Existing language strings for "edit," "save," "cancel," "attribute name," "global attribute title," and "global attribute description" have been reused where applicable.
Miro link to edit if needed: https://miro.com/app/board/uXjVLWs2W_0=/