On Tue, Dec 9, 2008 at 3:57 PM, Colin Bean <[EMAIL PROTECTED]> wrote: > Ah, didn't realize that it was showing one part of the page and not > another. Looks like the template tag in the "secondary" section > queries all of the blog post objects, while the main section uses the > "latest" variable from django.views.generic.date_based.archive_index. > According to the docs, "Objects with a date in the future are not > included (in latest) unless you set allow_future to True." > > http://docs.djangoproject.com/en/dev/ref/generic-views/#django-views-generic-date-based-archive-index > > Any chance the dates on your posts are set to the future? Is the date > set correctly on your server?
Those were my thoughts as well. Depending on how the date gets set when storing an item in the database, and what date/time gets used when pulling it from the db, you could run into issues here. Try passing allow_future=True in with the other arguments to the dict() Jay P. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
