, June 21, 2013 9:18:59 PM UTC-4, ayeowch wrote:
>>
>> TEMPLATE_CONTEXT_PROCESSORS is not there by default in your project's
>> settings.py. It's defined in the django/conf/global_settings.py, see
>> https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-T
On 22/06/2013 02:24, asax...@princeton.edu wrote:
# Make this unique, and don't share it with anybody.
SECRET_KEY = '8c(j)m3dm!m3gd_n#vjjfqdeuq!ltsj3+xii617dos1i@_pc7*'
You'll want to change your secret key now that you have posted it on a
public mailing list if you are actual
Thank you! I'm always amazed at how quickly and accurately people respond
in this group--much appreciated.
Alok
On Friday, June 21, 2013 9:18:59 PM UTC-4, ayeowch wrote:
>
> TEMPLATE_CONTEXT_PROCESSORS is not there by default in your project's
> settings.py. It's de
TEMPLATE_CONTEXT_PROCESSORS is not there by default in your project's
settings.py. It's defined in the django/conf/global_settings.py, see
https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-TEMPLATE_CONTEXT_PROCESSORSfor
the default callables that are included.
On Sat, Ju
Hey everyone,
Currently a noob to Django--I'm using Django 1.5.1 installed with Python
2.7 in a virtualenv. I'm learning about context processors and noticed that
TEMPLATE_CONTEXT_PROCESSORS is completely missing from my settings.py. Is
this normal? Am I supposed to add Django
Guys,
I solved. It's django-debug-toolbar fault. It's does double requests and
loads all the context processor :(
Thanx
2012/6/13 Ricardo L. Dani
> Hello everyone,
>
> I'm having a issue with template_context_processors requests and views
> that do not use the co
Hello everyone,
I'm having a issue with template_context_processors requests and views that
do not use the context processors, i.e. in a render_to_response without use
of RequestContext.
For example, in my TEMPLATE_CONTEXT_PROCESSORS, as default, I h
Never mind... one of the views was lacking a context_instance... :-P
Thanks!
On 12 out, 17:17, diogobaeder wrote:
> Hi there,
>
> I've being noticing something strange: I added a context processor to
> my project, but it's not being used when I run the project by
> "manage.py testserver". Why th
Hi there,
I've being noticing something strange: I added a context processor to
my project, but it's not being used when I run the project by
"manage.py testserver". Why that? Did I do something wrong?
When I run it in "runserver", it's working alright.
Thanks!
--
You received this message bec
f the projects that I am creating.
>
> The doc
> (http://docs.djangoproject.com/en/dev/ref/settings/#std:setting-TEMPLATE_CONTEXT_PROCESSORS)
> makes it seem as if this is pre-populated by default.
>
> $ python -c 'import django;print django.VERSION'
> (
Is this variable supposed to be present in default generation of
settings.py after a startproject? Because I don't see this variable in
any of the projects that I am creating.
The doc
(http://docs.djangoproject.com/en/dev/ref/settings/#std:setting-TEMPLATE_CONTEXT_PROCESSORS)
makes it seem
Hi,
I have this issue too :)
On May 17, 1:00 pm, stefan wrote:
> Hello,
>
> I have this issue, I am using the development Django version (checked
> out from svn). I use a template_context_processor and sometimes the
> context_processor is processedtwice,
> one for the current request and one for
Hello,
I have this issue, I am using the development Django version (checked
out from svn). I use a template_context_processor and sometimes the
context_processor is processed twice,
one for the current request and one for the referring/previous
request. I know this because I am using logging insi
I'm using django.contrib.auth.views for user management like login
wrapped in my own views for example:
@login_required
def password_change(request):
return django.contrib.auth.views.password_change(request,
template_name='userpanel/password_change.html')
But my template context processo
wrote:
>>> The goal is to have request.META.PATH_INFO in templates.
>>>
>>> The problem is that TEMPLATE_CONTEXT_PROCESSORS does not seem to make
>>> any difference. request is still not accessible from template. Even is
>>> I
>>> set the variable t
FO in templates.
>>
>> The problem is that TEMPLATE_CONTEXT_PROCESSORS does not seem to make
>> any difference. request is still not accessible from template. Even is
>> I
>> set the variable to () nothing happens.
>
> As far as I know, the TEMPLATE_CONTEXT_PROCE
On 7/24/06, Rares Vernica <[EMAIL PROTECTED]> wrote:
> The goal is to have request.META.PATH_INFO in templates.
>
> The problem is that TEMPLATE_CONTEXT_PROCESSORS does not seem to make
> any difference. request is still not accessible from template. Even is
> I
> set th
On 7/24/06, Rares Vernica <[EMAIL PROTECTED]> wrote:
> The problem is that TEMPLATE_CONTEXT_PROCESSORS does not seem to make
> any difference. request is still not accessible from template.
Are you sure you're using RequestContext in the view?
--
"May the forces of evil
Hi,
I added this to my settings.py:
TEMPLATE_CONTEXT_PROCESSORS = (
'django.core.context_processors.request',
'django.core.context_processors.auth',
'django.core.context_processors.debug',
'django.core.context_processors.i18n',
)
I t
On 6/10/06, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> Is there a list of attributes for an HttpRequest object somewhere?
http://www.djangoproject.com/documentation/request_response/
--
"May the forces of evil become confused on the way to your house."
-- George Carlin
--~--~-~--~
On Jun 10, 2006, at 12:32 PM, Luke Plant wrote:
>
> On Saturday 10 June 2006 16:40, Todd O'Bryan wrote:
>
>> so I'd like to add userinfo to the context by default. To do that,
>> I've figured out that I need to add my own function to
>> TEMPLATE_CONTEXT
On Saturday 10 June 2006 16:40, Todd O'Bryan wrote:
> so I'd like to add userinfo to the context by default. To do that,
> I've figured out that I need to add my own function to
> TEMPLATE_CONTEXT_PROCESSORS, but I'm a little confused how to get the
> currently
To recap, I have a UserInfo model that has User as a foreign key. I'm
getting tired of
{{ user.userinfo_set.all.0... }}
so I'd like to add userinfo to the context by default. To do that,
I've figured out that I need to add my own function to
TEMPLATE_CONTEXT_PROCESSORS, b
23 matches
Mail list logo
