#14977 closed Uncategorized (duplicate)
contrib.admin ordering by two or more fields
| Reported by: | Evan Carmi | Owned by: | nobody |
|---|---|---|---|
| Component: | contrib.admin | Version: | 1.3-alpha |
| Severity: | Normal | Keywords: | admin ordering order |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | yes | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The contrib.admin app does not support ordering by more than one field. The ordering list/tuple is always truncated to the first element ignoring all others. I recently ran into a situation where I needed to sort by two fields and found that the admin was unable to do this. I have created a patch that implements this feature. Feedback on the patch would be appreciated. Documentation and tests to follow.
Attachments (2)
Change History (8)
by , 14 years ago
| Attachment: | ticket14977.diff added |
|---|
comment:1 by , 14 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
comment:2 by , 14 years ago
| Needs tests: | set |
|---|---|
| Resolution: | duplicate |
| Status: | closed → reopened |
Not a duplicate, though there are plenty of duplicates out there: 4926, the UI example given.
comment:3 by , 14 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | reopened → closed |
comment:4 by , 14 years ago
| Severity: | → Normal |
|---|---|
| Type: | → Uncategorized |
I really don't understand why this is closed. This has been marked as a duplicate for #4926 but this in turn has been marked as a duplicate for #11868 because of a better approach and a more recent patch. The patch isn't even working on trunk and the whole approach wants way too much. Could we just submit this patch which would fix the underlying problem without trying to fix the ui?
comment:5 by , 14 years ago
| Easy pickings: | unset |
|---|
No, the UI's part of the issue and needs to be fixed as part of it. #11868 is looking fairly good, so if you want to move it along give the patch there a review, check that it covers your use case, and help update it to trunk if you can.
There's already a ticket open for this: #11868