> Any light to understand/solve it? With any sort of suspected caching problem (and this certainly smells like one), Step 1 is always to disable caching, restart the server, and see if the problem magically goes away. If it does, you can put away the Xanax and start looking at where and how you are invoking the caching system.
One thing you did not share with us was exactly *how* you are invoking caching. If you are using either the per-site caching middleware or the @cache_page decorator, then you are probably caching more than you realized. If *anything* on the page changes on a view-to-view basis-- even something as simple as a greeting to the user--then neither of these methods will not work for you. For a more fine-grained approach, look at the section on template fragment caching. (http://www.djangoproject.com/documentation/cache/ #template-fragment-caching) If you are trying to avoid an expensive DB operation, you can cache that in the view code. See the section on the low-level cache API for more on this. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
