Django

Code

Ticket #7094 (closed: fixed)

Opened 2 months ago

Last modified 2 months ago

Ordering in the admin has no effect after [7477]

Reported by: brosner Assigned to: nobody
Milestone: Component: Admin interface
Version: newforms-admin Keywords:
Cc: Triage Stage: Accepted
Has patch: 0 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

After doing a merge from trunk I have noticed that ordering in ChangeList is not taking affect. I have used pdb to determine that the correct data is being passed into order_by on the queryset, but not sure what is tripping it up. Creating a ticket so this issue is not lost and so that others are aware and may find a solution before me.

Attachments

Change History

04/27/08 07:27:03 changed by brosner

  • needs_better_patch changed.
  • stage changed from Unreviewed to Accepted.
  • needs_tests changed.
  • needs_docs changed.

04/27/08 07:51:45 changed by brosner

I am beginning to wonder if this was some odd merge problem that svnmerge did automatically somehow. It does work as expected in trunk's admin. The only differences between ChangeList in trunk and in newforms-admin is the API calls it needs to get to options for the admin interface for the model. Hopefully this information is useful to someone else if they look into this.

04/27/08 10:31:56 changed by brosner

  • status changed from new to closed.
  • resolution set to fixed.

(In [7481]) newforms-admin: Fixed #7094 -- Fixed admin ordering breakage after the queryset-refactor changes from trunk.

04/27/08 10:33:22 changed by brosner

ModelAdmin.queryset was passing no parameters to order_by which caused any future ordering to not happen.

Add/Change #7094 (Ordering in the admin has no effect after [7477])




Change Properties
Action