If you don't pass a cache timeout to {% chunk %}, the chunk contents will be cached forever (or until the cache runs out of space). I can't see how this would ever be desirable behavior. The chunk is being stored in the database so it can be modified at will, yet the default behavior prevents that from taking effect. I'd recommend merging in carljm@8dcf287e to rip out the caching support altogether. Users who want to cache the chunk can wrap it in {% cache %}.
Alternatively, the Chunk model should clear the cached value on save.
If you don't pass a cache timeout to
{% chunk %}
, the chunk contents will be cached forever (or until the cache runs out of space). I can't see how this would ever be desirable behavior. The chunk is being stored in the database so it can be modified at will, yet the default behavior prevents that from taking effect. I'd recommend merging in carljm@8dcf287e to rip out the caching support altogether. Users who want to cache the chunk can wrap it in{% cache %}
.Alternatively, the
Chunk
model should clear the cached value on save.