> It's not intended to work, so it seems like everything is behaving > correctly from that respect. The admin intentionally only orders on one > field. The reason being that the UI feedback for ordering on more than > one column is generally going to be confusing (nobody's come up with a > good way to represent it yet). > > If you have a look in > django.contrib.admin.views.main.ChangeList.get_ordering() you will see > where the single ordering field requirement is enforced. So you could > somehow override that method to get what you want, I guess. > > Regards, > Malcolm
Hi Malcolm, Thanks for the explanation. Given that the reason for only ordering on one field is that it's hard to design a UI to order on two, why not just allow ordering on more than one field for the default ordering, and then revert to single-field ordering when someone clicks the column headers? I'll poke around and find a dirty hack. Thanks for the pointer on the ChangeList.get_ordering()! -David Christiansen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
