#15564: PROPOSAL: nocache template tag to exclude parts of a template from being cached --------------------------+--------------------------- Reporter: izamojc@… | Owner: nobody Status: new | Milestone: 1.4 Component: Cache system | Version: SVN Keywords: template tag | Triage Stage: Unreviewed Has patch: 0 | --------------------------+--------------------------- In many cases, I'd like to just be able to turn caching on for a project and let it do what it does automatically 99% of the time. However, most sites have authentication, and most display a "login or signup" message that gets replaced by the user's name when they sign in. This is problematic for caching since it means that same page will be cached multiple times, once for each user who views it, defeating the purpose of the cache.
I propose a formal {% nocache %} ... {% endnocache %} template tag that can be wrapped around these "micro-dynamic" regions of the template. This way, blanket caching can be applied to the entire site, and these cache- busting problem areas can be dealt with in a precise manner. -- Ticket URL: <http://code.djangoproject.com/ticket/15564> Django <http://code.djangoproject.com/> The Web framework for perfectionists with deadlines. -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-updates@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.