On Aug 21, 12:34 pm, Bryan Fordham <bford...@gmail.com> wrote:
> Also tried switching to wsgi, just to see if it would make a
> difference. It didn't.
>
> I'm seriously stumped
Is the page truly blank? Ie., have you gone 'View Source' in the
browser to see what is returned. Are you sure you haven't stuffed up
something in global HTML template whereby missing a closing '>' for
HTML.
Since now using mod_wsgi, try wrapping the WSGI application for Django
in the LoggingMiddleware examples described in:
http://code.google.com/p/modwsgi/wiki/DebuggingTechniques
The second of those can be used to capture all the response direct out
of the WSGI application and may assist in helping you see what is
actually returned before the web server does anything with it.
Graham
> On Thu, Aug 20, 2009 at 3:56 PM, Bryan Fordham<bford...@gmail.com> wrote:
>
> >> Don't forget the comma after the absolute path. For example,
>
> >> '/home/bfordham/websites/bfordham/trunk/bfordham/blog/templates',
> >> <---- comma
>
> > Tried that, no change.
>
> > Changed the template path to an invalid path, same thing. Very weird
> > --
> > Thanks
> > --B
>
> --
> Thanks
> --B
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
