Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Payment method no longer have an editor

The prior payment method editor where title and description for each payment method could be edited is no more. This is not really plugin side decided, but based on rules set by Resurs Bank. First of all, titles and descriptions are handled by Resurs Bank to simplify changes that is related to whatever could happen to a payment method. The same goes for the sorting of payment methods in the checkout. Some payment methods is regulated by laws and should be displayed in a certain order. This is no longer up to the plugin to decide and sorting is based on in which order Resurs Bank is returning them in the API.  If you want anything changed, related to the payment method, you have to contact Resurs Bank support

Many features are lifted straight out from the eprior version

However, not all of them are. There are settings in this new version that is no longer working, especially features that is filter bound. Actions, filters, triggers lists everything new available for you.

Settings is almost similar to the old plugin

They are however set with new identifiers. It is partially intentional done, so we don't collide with old settings. Some of them are also not very effective, so some of them has also been removed as they did no longer fill any purpose, not even in the old release.

Instant finalizations
Jira Legacy
serverTornevall Networks
serverIdef1f2374-e58a-319f-9d38-10348dbac859
keyRWC-256

...

Jira Legacy
serverTornevall Networks
serverIdef1f2374-e58a-319f-9d38-10348dbac859
keyRWC-160

Race conditions in order status changes

A few weeks ago (from nov 28 2021) an important case was solved that handled order status changes and the priority order where order statuses could be a fight between two different places in the plugin: If the customer lands on the landing page first and changes the order status of the order, this could affect the callback if it was later. If the callback went of before the landing page, that could affect the status too. And if both events occurs exactly the same, there would be a status update war where stock handling if the main actor to be affected where stock is in risk of been drawn twice. RWC-87 below, is one part of this that thanks to the new solution could be cancelled. If there's any need for it again, we have it kept but cancelled.

Jira Legacy
serverTornevall Networks
serverIdef1f2374-e58a-319f-9d38-10348dbac859
keyRWC-87