Hi Nop Community:
I have been working / testing with Nop Commerce 2.8 version and while doing all these my understanding is if we use Nop Commerce cart/sfotware, we will have to do the website configuration each an every time we push a bug fix in production - this is because there is no way we can point a newer version (which contains small bug fix or enhancement) of Nop 2.8 to the current / existing database.
Atleast this is my understanding and it could be wrong and just wanted to understand how to avoid this huge effort of cart configuration every time we put a small fix/feature in production. There could be another way of updating only binaries, but I have noticed that system gives error messages in case we refresh a few binaries only.
Please share your thoughts how do you all do this in your day / today activities.
Regards,
I just had an experience of fixing a ccavenue (payment gateway) issue and was wondering how best we an avoid to reconfigure all the site and push the fix in current test environment.