Re: .views._CheckLogin.__call__ didn't return an HttpResponse object
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 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 -~--~~~~--~~--~--~---
Re: .views._CheckLogin.__call__ didn't return an HttpResponse object
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 return anything? -- DR. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: .views._CheckLogin.__call__ didn't return an HttpResponse object
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 function that handles mail. Cheers, Ryan On Jul 14, 6:33 am, alecs wrote: > 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 foo(request,username) view > into your big view, but I don't think it's a correct solution. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: .views._CheckLogin.__call__ didn't return an HttpResponse object
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 foo(request,username) view into your big view, but I don't think it's a correct solution. --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: .views._CheckLogin.__call__ didn't return an HttpResponse object
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 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 -~--~~~~--~~--~--~---
Re: .views._CheckLogin.__call__ didn't return an HttpResponse object
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 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
-~--~~~~--~~--~--~---
Re: .views._CheckLogin.__call__ didn't return an HttpResponse object
Are you returning render_to_response in the view? On Jul 14, 6:12 am, alecs 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_to_user(request,username,dummy) The > mail_to_user view contains render_to_response and if I simply copy the > contents of mail_to_user into main view everything works OK. But I > think it's better to call another view than to copy a whole conent. > What can be wrong ? --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
