This is intended behavior and documented in the generic view
documentation here:
http://docs.djangoproject.com/en/dev/ref/generic-views/#django-views-generic-date-based-archive-year
It states that this view raises a 404, when the queryset is empty, so
the resulting page basically is considered em
Ok, it turns out that the "archive year" generic view throws a 404
error if the querset commands result in an empty set. Through testing
I discovered that my development server database works fine because
the queryset returns values, but the live database throws a 404
because it returns with an em
Sorry! This application is running using:
Django (1.0.2)
mod_python (3.3.1)
Python (2.5)
Interestingly, if I try this url:
http://realvelour.com/blog/2009/01/
it works on the live server, but does not display any entries from
that month (January). I'm wondering if the queryset is empty or
some
I'm running a Django blog on Webfaction using the Byteflow engine, and
I'm having an issue where this url:
http://realvelour.com/blog/2009/
works fine on my development server (the default Django dev server),
but triggers a 404 error on the real Apache server. My site has been
running for a whil
You don't say whether you are using mod_python, mod_wsgi or fastcgi.
Knowing may be important.
Graham
On Mar 31, 11:59 am, dls wrote:
> I'm running a Django blog on Webfaction using the Byteflow engine, and
> I'm having an issue where this url:
>
> http://realvelour.com/blog/2009/
>
> works fin
5 matches
Mail list logo
