-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Prabhu,
Let's establish the reason the 404.html doesn't show on a supposed 404
error; that is because every single request on the output you posted a
little while ago from the server is responded with a 500 error.
Something is fouled up with the vie
Hi Luke,
Thanks for your email. The particular source is already fine with
no /. I also tried adding slash assuming you swapped the particular
line in your email.
Can you give another shot and let me know if you can spot something?
Regards,
Prabhu
On Jul 30, 6:46 pm, Luke Seelenbinder
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey, I think I located your problem.
In file invoicy / guidy / urls.py
You should change the first url pattern to read:
url(r'^/$', 'guidy_default', name='guidy-default'),
instead of:
url(r'^$', 'guidy_default', name='guidy-default'),
That should f
Hi Karen,
Thanks for replying. I have put my 404.html in the same place as that
of 500.html. To make sure, I even copy pasted 500.html and changed the
error message text alone.
Here is an output from the django development server, when I tried to
access "sdfsa" (Invalid url)
[30/Jul/2009 18:25:
On Thu, Jul 30, 2009 at 8:40 AM, prabhu S wrote:
>
> Hi All,
>
> I am not noticing a weird issue in django 1.1. When DEBUG is true in
> settings and if I try a non-existent url, django shows me a friendly
> 404 page. Now I create 404.html and 500.html and place this in
> templates directory. Then
Hi All,
I am not noticing a weird issue in django 1.1. When DEBUG is true in
settings and if I try a non-existent url, django shows me a friendly
404 page. Now I create 404.html and 500.html and place this in
templates directory. Then If I turn off debug and try a non-existent
url, I expect to se
6 matches
Mail list logo
