London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!

Quan Mai
Oct 12, 2016
  5181
(7 votes)

Quicksilver "2.0" released

We have released Quicksilver "2.0". The actual version number is not "2.0", but from now on, the version of Quicksilver will more or less match with the version of Episerver Commerce, when it is released.

A new major version means breaking changes - and in "2.0" we changed a lot of things:

- We completely moved to the new promotion system/new order abstraction API:s. Our vision is that's the way forward and we highly recommend you to make the move when you have chances.

- We improved multi-shipment feature. Multi-shipment was added in Quicksilver 1.4, but now it's refined and tuned for even better user experience.

- We restructured the project and refactored controllers and services to make them even more testable. More tests were also added.

- Plenty of other bug fixes and improvements.

Image Quicksilver20.PNG

Quicksilver "2.0" is simply the biggest update to Quicksilver since it was introduced last year. Quicksilver has been a favourite sample template in Commerce developer community, and we are sure you'll love Quicksilver "2.0" even more. Download it today from Github: https://github.com/episerver/Quicksilver/

Oct 12, 2016

Comments

mounir.boudouda
mounir.boudouda Oct 12, 2016 04:01 PM

Hi

Github Quicksilver is still version 1.4.

Quan Mai
Quan Mai Oct 12, 2016 05:21 PM

Hi,

It's in the develop branch now https://github.com/episerver/Quicksilver/tree/develop 

Will be shortly merged to master 

Oct 12, 2016 07:54 PM

Great news!

Simon Mercer
Simon Mercer Dec 16, 2016 12:27 PM

Are we still able to use the Legacy Promotions system in Quicksilver?

I realise that we sohuld be moving away from it, but I've got some issues with a current implementation and I wanted to make some tests against it.  I've disabled it via Features in app.config and i'm able to create/edit promotions.  I don't seem to get them calculating as expected.  I assume the correct workflow is being used when I disable the new system?

Simon Mercer
Simon Mercer Dec 16, 2016 04:45 PM



needs to be added in both CMS and Commerce Manager site ecf.app.config.

Promotions Manager is accessible in CommerceManager, but the promotions aren't processed correctly - am I missing a setting?

Quan Mai
Quan Mai Jul 6, 2017 09:22 AM

@Simon Mercer: Sorry for the very late reply. Quicksilver does not use the old promotion engine at all. It only works with the new promotion system - as mentioned in the post. You can manage the promotions in Marketing UI 

Please login to comment.
Latest blogs
Natural Language Q&A in Optimizely CMS Using Azure OpenAI and AI Search

In Part 2, we integrated Azure AI Search with Azure Personalizer to build a smarter, user-focused experience in Optimizely CMS. We used ServiceAPI ...

Naveed Ul-Haq | Apr 25, 2025 |

Identifying Spike Requests and Issues in Application Insights

Sometimes within the DXP we see specific Azure App Instances having request spikes causing performance degredation and we need to investigate. I fi...

Scott Reed | Apr 25, 2025

Optimizely Frontend Hosting Beta – Early Thoughts and Key Questions

Optimizely has opened the waitlist for its new Frontend Hosting capability. I’m part of the beta programme, but my invite isn’t due until May, whil...

Minesh Shah (Netcel) | Apr 23, 2025

Developer Meetup - London, 21st May 2025

The London Dev Meetup has been rescheduled for Wednesday, 21st May and will be Candyspace 's first Optimizely Developer Meetup, and the first one...

Gavin_M | Apr 22, 2025