Is there any way I can get a response on this? I really hate to be  
annoying and pedantic, but the following problems are literally show- 
stopper problems for my Django projects and they're holding up what  
is otherwise a working project. I would really appreciate something -  
anything!

Regards,
Tyson

On Jul 16, 2006, at 2:10 PM, Tyson Tate wrote:

>
> Note: I originally posted part of the following to the users list,
> but I realized today that it's probably better posted here because it
> deals with a potential bug and developer rationale behind some
> generic view behavior that I find very odd. Sorry for the cross-post!
>
> ---
>
> Using the latest SVN on MacOS X 10.4.7 with MySQL 5.0.22 and Python
> 2.4.3:
>
> I've built a simple date-based app that works fine through the admin
> and all proper URLs resolve to the correct template and display the
> correct data. I reset the SQL for the project, ran 'syncdb' and then
> ran it with 'runserver'. I added one object with a date and time of
> today through the admin interface.
>
> 1. In the date_based.archive_index view, the 'date_list' object is
> empty. It should have a date object for this year because there is,
> of course, a post in the current year (2006). The docs for this extra
> context variable state that this should contain: "all years that have
> objects available according to queryset". This smells like a bug to
> me. Can anyone confirm?
>
> 2. Both 'archive_month' and 'archive_day' generic views set
> 'previous_month' and 'previous_day'  even when there are no previous
> months/days in the current view. This is documented as expected
> behavior. Can anyone supply the rationale for this? Unless I'm
> missing something, it's completely illogical to do this. Why tell the
> templates that there's a previous month/day when there really isn't?
> If there's no next month or day, next_month/next_day is correctly set
> as empty as you would expect, but not previous.
>
> I'd like to use the following in my month template:
>
> ---
> {% if next_month %}
>       <li>Previous Month: <a href="/articles/{{ next_month|date:"Y/M/"|
> lower}}">{{ next_month|date:"F Y"}}</a></li>
> {% endif %}
> {% if previous_month %}
>       <li>Next Month: <a href="/articles/{{ previous_month|date:"Y/M/"|
> lower}}">{{ previous_month|date:"F Y"}}</a></li>
> {% endif %}
> ---
>
> Thanks in advance for any help/suggestions,
> Tyson Tate

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---

Reply via email to