Here's dangerous scenario that may occur if you are not using settings.py's
LIVESETTINGS_OPTIONS parameter with 'DB': False, as described
was the case for me until I encountered the issue I am about to
-You create / use some tax module, let's say tax.modules.area
-In livesettings (yourshop.com/settings) , you set the tax module to "Area"
-Your shop goes live
-When the users does a checkout, the systems makes a DB request to find out
what tax module it should be using ->
-The DB request fails for some reason (dropped connection because of traffic
-Instead or Excepting, the systems defaults to the "NO TAX" module set as
default in satchmo tax's config.py. I think this is caused by this piece of
-User checks out and *pays no taxes!!*
Important: This can happen for anything that depends on Livesettings, it can
affect shipping, taxes, payment, discounts....
So I strongly suggest that you use LIVESETTINGS_OPTIONS in production,
otherwise you will notice some very erratic behavior during peak time.
In addition, if the only reliable solution is to use LIVESETTINGS_OPTIONS,
why not simply drop django_livesettings and hard-code the configuration in
the settings.py file?