Re: .views._CheckLogin.__call__ didn't return an HttpResponse object

2009-07-14 Thread alecs
Thanks. I thought this called view will do render_to_response ... --~--~-~--~~~---~--~~ 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

Re: .views._CheckLogin.__call__ didn't return an HttpResponse object

2009-07-14 Thread Daniel Roseman
Please don't snip the context. On Jul 14, 11:24 am, alecs wrote: > I'm just calling another view mail_to_user(request,username,dummy) , > which contains render_to_response! OK, think what happens when you return from that view: you go back to the calling view. Does that

Re: .views._CheckLogin.__call__ didn't return an HttpResponse object

2009-07-14 Thread Ryan K
I'm not really sure I understand your question but you don't need to jump to another view...you just need to pass the relevant objects to the mailer function and then "return render_to_response(...)." If the mailer function is already in another view, refactor the code and create a non view

Re: .views._CheckLogin.__call__ didn't return an HttpResponse object

2009-07-14 Thread alecs
Ok, a simple question: Are there any possibilities to call from current view another view. For instance you have a large view and in the middle of it you need to perform THE SAME actions which are already defined in def foo (request,username). Of course, you can copy the contents of

Re: .views._CheckLogin.__call__ didn't return an HttpResponse object

2009-07-14 Thread alecs
I'm just calling another view mail_to_user(request,username,dummy) , which contains render_to_response! --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to

Re: .views._CheckLogin.__call__ didn't return an HttpResponse object

2009-07-14 Thread Ryan K
To be a little more explicit, perhaps your view code contains: render_to_response('template.html",{},RequestContextInstance) as opposed to return render_to_response(...) Cheers, Ryan --~--~-~--~~~---~--~~ You received this message because you are subscribed to

Re: .views._CheckLogin.__call__ didn't return an HttpResponse object

2009-07-14 Thread Ryan K
Are you returning render_to_response in the view? On Jul 14, 6:12 am, alecs <alecs@gmail.com> wrote: > Hi all :) Can u help me with .views._CheckLogin.__call__ didn't return > an HttpResponse object . I'm trying from my view 'jump' to another > view by calling     mail_

.views._CheckLogin.__call__ didn't return an HttpResponse object

2009-07-14 Thread alecs
Hi all :) Can u help me with .views._CheckLogin.__call__ didn't return an HttpResponse object . I'm trying from my view 'jump' to another view by calling mail_to_user(request,username,dummy) The mail_to_user view contains render_to_response and if I simply copy the contents