On May 12, 2007, at 9:57 PM, Malcolm Tredinnick wrote:
> This could be as simple as a mismatch between documentation and code
> version.
Thank you, Malcom. I downloaded the current version, 0.96, and
installed it.
When I call the django.fcgi using "http://localhost/cgi-bin/
django.fcgi", I
On Sat, 2007-05-12 at 13:29 -0700, Mark Phillips wrote:
> Thank you, Don. I understand what Malcolm wrote. I didn't include the
> trace back and that was indeed a mistake.
>
> After walking through the set up and making some adjustments
> to .htaccess, I stopped getting a trace back in the br
Thank you, Don. I understand what Malcolm wrote. I didn't include the
trace back and that was indeed a mistake.
After walking through the set up and making some adjustments
to .htaccess, I stopped getting a trace back in the browser. Thus, I
didn't have much to share with Malcolm.
This mor
You stated you got a python traceback and yet you only show us the
error message. What Malcolm was trying to say was that it would be
helpful to print out that traceback, rather than your Apache
configuration, at least to start with.
When debugging a problem it's always best to start with t
On May 11, 2007, at 9:40 PM, Malcolm Tredinnick wrote:
> More information is definitely needed here. You've just done the
> equivalent of "I've had a car accident." "Where should we send the
> auto
> service?" "There's a traffic light here."
Thanks for the reply, Malcolm.
--~--~-~--~
On Fri, 2007-05-11 at 09:59 -0700, Mark Phillips wrote:
> I attempted invoking the django.fcgi script directly with a URL. E.g.
> "http://dev.mysite.com/cgi-bin/django.fcgi";. I tried this because I
> am still having trouble using a normal url like "mydjango.mysite.com"
> or similar. For exa
6 matches
Mail list logo
