Middleware Documentation still refers to CacheMiddleware

[anonymous]

On the Cache documentation page, it says you have to use UpdateCacheMiddleware and FetchFromCacheMiddleware instead of the older CacheMiddleware. However the Middleware documentation only mentions CacheMiddleware and does not discuss the two new middlewares.

[James Bennett]

Most people can still use CacheMiddleware, and CacheMiddleware still exists; it's just in certain situations -- as described in the caching docs -- that you need to use the separate bits to avoid problems.

[Malcolm Tredinnick]

This isn't a good default strategy. You can still use CacheMiddleware is it's working for you now or you really know what you're doing. It's far safer to use the split version, though, since it means you can safely add other middleware later without having to hurt your brain trying to work out if it's something that will affect the cache key. It's an omission in the middleware docs, in any case, since these two middleware pieces exist.

[Antti Kaihola]

patch for middleware documentation

[James Bennett]

(In [8791]) Fixed #8698: Updated overview docs for cache middleware to show that it's been split into two classes

[Jacob]

Milestone 1.0 deleted