Limio Release Notes - Release 79

Summary

- Bug fixes: Rich text improvements, accurate payment detail changes and / route consistency.

New Features and Improvements

Stability Improvements

We've made some architectural improvements such as aligning the Shop and Limio Commerce app to both use the same API, and upgrading the version of react-router being used. There won't be any user facing changes but this will help make Limio Commerce more reliable and stable.

Bug Fixes

Update correct payment details in Zuora

Previously when a customer updated their payment details in Limio, as a default, this would update the most recent payment method used. Customers with multiple subscriptions could have multiple Zuora accounts and multiple payment methods, which meant updating the most recent card could be an incorrect and unintended change. This is now fixed and the correct payment will be updated for customers with multiple Zuora accounts — i.e. multiple subscriptions.

(Zendesk ticket #3153)

/ route not showing the same details as /default route

If a customer made changes to the /default Campaign (adding a new offer, changing the price), these changes were not reflected in the / Campaign. This is now fixed so that changes made to the / route will reflect in the /default route and changes made to the /default route will reflect in the / route.

Last rich text change not saved

If a customer made a change to a rich text field and clicked Save, the changes would not be saved. The workaround for this issue was to click into another rich text field before clicking Save. This is now fixed and changes to rich text fields can be saved straight away without clicking into another rich text field.

Please note this was retroactively deployed into Releases 77 and 78 as well. After Release 79, this fix will be included in all releases without redeployment.

(Zendesk tickets #3256, #3266)

Endless loop when editing components with rich text props

Previously, clicking the edit pencil in the Page Builder caused components with rich text props to render incorrectly. This issue has been fixed so that rich text values can be changed and render as expected. This includes styling the rich text in bold, italics, and with links.

Cannot build Campaigns if image format is without extension

It is not possible to build a Campaign if an image format does not have an extension. Now any unknown image is saved with a .img extension to enable Campaigns to be built.

Please note this was retroactively deployed into Releases 76 and 79. After Release 80, this fix will be included in all releases without redeployment.

(Zendesk ticket #3327)

Nexi Billing Component not rendering in Page Builder

The Nexi Billing component was not being displayed as a preview in the Page Builder. This is now resolved.