Table sort is currently broken on admin/content.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | admin_content_overview.png | 7.08 KB | sivaji_ganesh_jojodae |
| node-header.patch | 552 bytes | jody lynn |
Table sort is currently broken on admin/content.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | admin_content_overview.png | 7.08 KB | sivaji_ganesh_jojodae |
| node-header.patch | 552 bytes | jody lynn |
Comments
Comment #1
heather commentedI tested this out.
On a fresh install from HEAD, yes, the content listing page was not sorting on the sortable columns.
After a fresh install and applying the patch, the columns sort.
wd!
Comment #2
jody lynnThanks for confirming!
Comment #3
webchickCommitted to HEAD. Thanks!
Comment #7
jody lynnComment #8
tszming commentedHave installed the 7.x-dev (2010-Aug-29), seems there is a regression:
1. Install 7.x-dev (2010-Aug-29), with standard profile
2. Create two articles in order, Test1 & Test2
3. In the URL, http://www.example.com/admin/content?sort=desc&order=Updated, expected order should be:
Test2
Test1
But the order showed:
Test1
Test2
4. Have further checked the node.admin.inc, the $nids returned are in correct order, so there must be some codes which altered the order after that query
Comment #9
sivaji_ganesh_jojodae commented#8 is true, see the attachment for proof. Changing the title to reflect the bug.
Comment #10
rayasa commentedThe bug lies in the form system.
Check the patch at #847852: Table Sort Doesn't Quite Sort
Comment #11
heine commentedRestoring issue status. The problem experienced in #8 is caused by another problem. This is handled in #700380: Regression: Tableselect sorting is altered if '#weight' is not set.