12 Jul 2019 by Marcin Gębala
June Release: Avalara Integration
Welcome to the June 2019 release of Saleor!
- We've integrated Avalara so Saleor now supports tax calculations in most major markets around the globe
- There are new functionalities and improvements in the payments section, including the ability to store credit card details
- Our Vouchers section has been reworked from scratch and is now as sleek and usable as any e-commerce can offer, as well as having an expanded range of offers you can make to your clients
Saleor has, to date, only supported tax calculations for the EU with Vatlayer. To support taxes in other countries, we’re integrating the popular Avalara tool with Saleor in this release! With Avalara enabled and configured, you’ll get proper tax calculations during the checkout process. Your orders will also be accessible in the Avalara admin panel.
Storing Credit Cards
We’ve improved the internal payment gateway interface, which now allows for storage and reuse of customers’ payment sources, such as credit cards, if the gateway supports it. Additionally, we’ve implemented support in the Braintree gateway module and plan to add Stripe very soon.
Improved Vouchers Section
Good user experience is always one of our top priorities. We are constantly testing Saleor and decided that the Vouchers section was quite challenging to use, so we set about designing an interface that would make it easier for you to quickly create attractive sales offers for your customers. We have now gathered common settings into visual cards, which makes for a clean and intuitive UI.
Refreshed Vouchers section in Dashboard 2.0
CSRF Vulnerability Fix
This release fixes a security issue that was introduced in version 2.7.0. In that release, we made customizations to the Django middleware in order to disable some elements that were unnecessary for requests coming to the GraphQL API. Unfortunately, we inadvertently disabled CSRF protection for all POST requests coming to static Django views in Storefront 1.0 and Dashboard 1.0. An attacker could therefore send a request without the valid CSRF token, and the server would accept it. In this release, to close this loophole, we’ve reverted to the original middleware configuration. We felt that the performance gain was minimal and it wasn’t a crucial feature for the system, so the original solution is acceptable.
All users of the affected version are encouraged to upgrade Saleor immediately.
These are the highlights of the release. For the full changelog, go to the Github release page.
This month we need to give 5,000 thanks 🙏 to all contributors, stargazers, and supporters of Saleor! We’ve just hit that landmark number of GitHub stars. It’s not all about the numbers, but it is nice to track how far Saleor has come with your constant support. Here’s a little GIF we made to celebrate the occasion.
For those of you who are interested in contributing to the project, we prepared a bunch of issues labeled as help wanted. Don’t worry if you don’t fully understand the problem — our team will try to guide you and answer all your questions. Remember to check our channels on Gitter and Spectrum; they serve best if you have quick questions that don’t require opening an issue on GitHub.