When switch to a flat 404 page without using a handler404 it works fine. Not sure if this a bug in Django because the above method used to work fine, but now it doesn't.
On Thursday, May 30, 2013 4:29:33 PM UTC-4, jayhalleaux wrote: > > So I am having issues with my 404 errors. > > When I manually throw a 404 error, my handler404 works fine and catches > the error showing my custom 404 error page. > > > http://tracklist.us/archive/event/1000/2012-12-05-sasha-moonpark-xxv-costa-salguero/ > > Now when I use a bad url which should be caught with my handler i get: > > http://tracklist.us/archive/tracklist/1000/ > > I get a server error. > > I get the following error in my logs. raise Resolver404: {u'path': > u'archive/tracklist/1000/', u'tried': my entire regex path} > > Not sure why I am catch 404 errors but not the resolver 404 errors. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
