#27882: Allow template fragment caching for unlimited time
-------------------------------------+-------------------------------------
Reporter: MikiSoft | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Template system | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by MikiSoft):
Replying to [comment:1 Tim Graham]:
Yes, I'm sure that it's not a problem in my project because I've tested my
project on this this way:
Fist, I put in a view
`print(cache.get(make_template_fragment_key('test')))` and in
corresponding template `{% cache 0 test %}`, then I started the server and
I opened to that page. It printed me `None`, even after refreshing the
page.
So, I changed tag to be `{% cache 300 test %}` and I've opened that page
again. And suddenly it started printing content which I put under that
cache tag!
--
Ticket URL: <https://code.djangoproject.com/ticket/27882#comment:2>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.c77e4209b0068906cbfe16c968f080ec%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
