Closed kousu closed 7 years ago
Upon a moment's reflection, I suppose that the intent here was for an falseish or missing value to trigger the fallback; it's a mistake that the simple existence of the value should be trusted. So that way the default value would do something sensible.
Fixed in PR #45
Our docs claim that
CACHE_MULTISITE_KEY_PREFIX = ""
is its default value, but if you actually set that in your settings file this test fails:The code that handles this is tangly and terrible and is literally in a file called "hacks.py":
It's not clear to me who is wrong here: hacks.py or the documentation of what it's supposed to do. Does anyone have any experience with
CACHE_MULTISITE_KEY_PREFIX
? What are your thoughts? If there's not much enthusiasm for it I intend to remove it to curtail the convoluted configuration space.