You cannot use the interface at admin/content/node to delete content which was dynamically generated at the same time.
Steps to reproduce:
1. Use a module (like Deadwood) on localhost which produces a lot of nodes at the same time. Many of these will have exactly the same timestamp.
2. Try and delete/modify these nodes using the UI provided at admin/content/node
Reason why this is happening:
It seems that when a query is ordering by a field which has non-unique values, MYSQL seems to return a random ordering instead.
Solution:
Add an ",n.nid ASC" to the query since we know the nid of the node will always be unique.
See supplied patch.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | node-admin-ordering-d6.patch | 1.24 KB | brianV |
| node.admin_.inc_.patch | 826 bytes | dwees |
Comments
Comment #1
dwees commentedChanging the title since this problem exists for more than just node deletion.
Comment #2
dwees commentedThe reason is because the timestamp for all of the nodes is used for the sort order, and for many sites content is created in batches, through an import or some other similar process. This problem also exists for the admin/user/user page and for similar reasons.
Comment #3
brianV commentedI would suggest we just handle the node.admin.inc change first, and worry about changes to the user sorting in a different issue, since it is more complex.
Rerolled the patch for D6 HEAD.
Note: this cannot be done in D7 and backported, since there is a major code change in D7.
Comment #4
jvieille commentedWe are in D6.14, but the problem seems still there:
mass-created nodes cannot be mass-modified in admin/content/node
Comment #5
thedavidmeister commentedPatch in #3 looks like a reasonable fix but no longer applies.
error: node/node.admin.inc: No such file or directory