On Dec 5, 7:02 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > If you're using CACHE_MIDDLEWARE_ANONYMOUS_ONLY you need a different > middleware ordering, as the error message says. That setting is a real > hack and I'd love to implement it in a better way some day. At the > moment, though, where you place thecachemiddleware depends on whether > you're using that setting or not. >
I am thinking about customizing a version of CacheMiddleware such that all views are cached unless the user is a staff member. If I were in charge, I would implement CacheMiddleware without the ANONYMOUS_ONLY hack and then also supply AnonOnlyCacheMiddleware and my own NonStaffCacheMiddleware as alternatives. This approach would be less hacky and the instructions about ordering Middleware would also be more straightforward to communicate. Anyone think thst the NonStaffCacherMiddleware will run into problems? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
