#2386: previous_month and previous_day are non-empty even if there are no
objects
in previous months/days
---------------------------------------------------+------------------------
Reporter: Tyson Tate <[EMAIL PROTECTED]> | Owner: jacob
Type: defect | Status: new
Priority: normal | Milestone:
Component: Generic views | Version: SVN
Severity: normal | Keywords:
previous_month previous_day genericviews
---------------------------------------------------+------------------------
Yes, I know this is documented behavior, but it is completely illogical.
In the {{{django.views.generic.date_based}}} generic views,
{{{previous_month}}} and {{{previous_day}} are not empty when there are no
objects in previous months/days. {{{next_month}}} and {{{next_day}} are
empty when there are no next months and days, which is logical.
I'd expect {{{previous_month}}} and {{{previous_day}} to be empty when
there are no objects in the previous months/days. How else are you
supposed to implement date-based navigation?
--
Ticket URL: <http://code.djangoproject.com/ticket/2386>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
