Added options to turn off separate cache for:
Sometimes cache is the same and there is no reason to store multiple cache entries with the same content. Each segmentation criteria can be turned off on cache settings form. By default they are all enabled. The only thing we didn't tested is upgrade from previous version without this settings. Probably missing setting will not be filled with default, so we'll have no segmentation at all on upgrade (which is very bad). Anyway, this needs testing.
Probably it should be implemented in Views project, but we've created patch for Views Content Cache. Patch was made from 6.x-2.2.
| Comment | File | Size | Author |
|---|---|---|---|
| views_content_cache-6.x-2.2-cache-segmentation.patch | 3.25 KB | dmitriy.trt |
Comments
Comment #1
steven jones commentedThis really should go upstream into views.
Comment #2
johnvAnother use case is here: #1606292: Share result-cache between displays with same results and different output
That issue creates 1 cache for several displays with the same query.
Comment #3
mustanggb commented