Hi Justin - Thanks & sorry I missed your email until just now. I did try
that, and it's interesting: it worked for any of the date based generic
views that took a datepart parameter in the url, i.e. archive_year,
archive_month, and archive_day. But archive_index just ignores it. Also
tried adding an order_by to the model, which had the same effect. I'm out
of my league but am guessing that the archive_index sets its own order by,
perhaps in a custom query via the date_field solely ..
I've kinda given up on this one and just came up with a different look and
feel for the site to promote featured blogs.
Thanks again,
Joe
On Tue, Jun 9, 2009 at 12:52 PM, Justin Myers <masterb...@gmail.com> wrote:
>
> Have you tried this yet?
>
> info_dict = {
> 'queryset': Entry.objects.order_by(-featured),
> 'date_field': 'pub_date'
> }
> urlpatterns = patterns('django.views.generic.date_based',
> ...
> (r'^$', 'archive_index', info_dict),
> )
>
> I haven't checked whether or not it works, but it seems like it'd do
> the job.
>
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
