greetings,
i have been working on a template loader to retrieve templates from the
database. after integrating the loader to work with the django's
admin, i now serve up templates from both the file system and the
database, for both the public and admin sites. one problem, however,
is with templatetags that retrieve django template code from the
database. the root of the problem is that the templatetags use the
Context object rather than the RequestContext object, which contains
all of the information contained in the TEMPLATE_CONTEXT_PROCESSORS
tuple stored in the settings.py file. so, for example, the auth object
is unavailable to me, which means i cannot use a code block like:
{% if not user.is_anonymous %}
logout
{% else %}
login
{% endif %}
which is stored in the database and which i retrieve using a
templatetag. in my template tag, i tried to over-ride Context with
from django.template import RequestContext as Context
and i did the same in my views file, but neither worked. i read in the
documentation that generic views use the RequestContext by default, but
my pages that use generic views were not rendering the templatetag
properly either. the rendering process for templatetags happens long
after the view phase, it seems.
can anyone suggest a way to force the use of RequestContext instead of
Context when creating template tags?
thanks in advance.
yours,
steve
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
