I'm using the extra_context dictionary passed into the view like many
folks (James Bennett among them) seem to recommend either directly or
via his projects.
Here is what a view might look like (all of this is on dpaste with
link below if you'd prefer):
from django.shortcuts import render_to_response
from django.template import RequestContext
def test_view(request, template_name='test_view.html', extra_context=
{}):
if request.method == 'POST':
print 'inside post code...'
extra_context['extra_context_test'] = 'this is a test message'
context = RequestContext(request)
for key, value in extra_context.items():
context[key] = callable(value) and value() or value
return render_to_response(template_name,
{'form': None},
context_instance=context)
Here's the template I'm using as well:
<html>
<body>
<form method="POST" action="/test_view/">
Here is the current value of the extra_context item 'test': <b>
{{ extra_context_test }}</b>
<input type="submit" name="Submit"/>
</form>
</body>
</html>
Now, if I call this view for the first time, I get something like this
in my browser (as expected):
Here is the current value of the extra_context item 'test':
[SUBMIT_BUTTON]
I click the submit button and then I get something like this:
Here is the current value of the extra_context item 'test': this is a
test message [SUBMIT_BUTTON]
So far so good. Based on my view this is exactly what I'd expect.
Now. Open a completely new browser if possible (I did this with
Firefox for the first two steps and then IE for this next step -- all
on the same Windows XP box) and navigate to the same view (in my case:
http://127.0.0.1:8000/test_view/).
Yep, you get this again:
Here is the current value of the extra_context item 'test': this is a
test message [SUBMIT_BUTTON]
NOTE: Existence of "this is a test message" text -- even though I
didn't POST it this time.
I have ensured that the POST portion of the view is not being called
and yet the extra_context_test value in the extra_context dictionary
still seems to have a value lingering.
Now I assume that somehow magically extra_context is still in the
request object or something, but I can't explain why.
If I just move the extra_context piece out of the parameters,
everything is ducky:
def test_view(request, template_name='test_view.html'):
# THIS WORKS AS EXPECTED BUT DOESN'T ALLOW ME TO PASS STUFF IN!!!
extra_context={}
if request.method == 'POST':
print 'inside post code...'
extra_context['extra_context_test'] = 'this is a test message'
context = RequestContext(request)
for key, value in extra_context.items():
context[key] = callable(value) and value() or value
return render_to_response(template_name,
{'form': None},
context_instance=context)
I feel certain that there is some bigtime obvious Python or Django
reason for this behavior but I've not found it.
Thank you very much for any explanation you are able to provide.
Best,
Keyton
Code here: http://dpaste.com/18518/
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
