On Fri, Apr 16, 2010 at 6:52 PM, Daxal <daxal.someone...@gmail.com> wrote: > Hi, > > None of my other views have RequestContext in them and they are > passing in the same variables. I am one of those programmers that come > in succession trying to figure out what the previous one was trying to > do. and this guy didn't even put any comments on it. so it takes me a > longg time to try to understand whats going on. > > sorry if my questions sound really dumb. > > in regards to the same question, I am very sorry about that. I was not > getting any replies (probably my impatience) ... won't happen again. > sorry. > > right now i am trying to figure this thing out using two approaches > (one is using modelform and second is just putting fields in the form > - the more traditional approach) > > thank you for your help > > p.s. any other suggestions? i am searching on web really clueless as > to what's happening. >
Well, computers aren't magic. They do precisely what you instruct them to do, and given the same input and the same function, produce the same output. In your traceback, your template tag is failing when it tries to look up the session in the template context. Variables are typically put into the context either directly, or by a template context processor. Template context processors are run when you create a RequestContext and pass that as the context to the template renderer. If it isn't being put into the context by a template context processor, then it must be being put into the other contexts directly in the view. Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
