Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Reproduce:
- Create a first node.
- Create a second node.
- Go to admin/content, click "edit" link for the FIRST node, re-save it, get redirected to admin/content.
- You see: The just updated node BELOW the second node, but it is newer. Also having an UPDATED marker, but you updated it yourself. (!)
- Click "edit" link for the SECOND node, re-save it, get redirected to admin/content.
- You see: The just updated node BELOW the first (previously updated, i.e., older) node. Also having a NEW marker. (?!)
How much can go wrong when we are missing automated tests? ;)
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | drupal.node-admin.4.patch | 2.31 KB | sun |
| #3 | drupal.node-admin.3.patch | 2.85 KB | sun |
Comments
Comment #1
Sivaji_Ganesh_Jojodae CreditAttribution: Sivaji_Ganesh_Jojodae commentedI can reproduce this, the updated node appears at the bottom instead of top. I guess this is because the table sorter is incorrect and it is already reported here #613666: Sorting on admin/content table is incorrect.
I disagree with the point #6, NEW marker for updated node it is not the case for me.
Comment #2
gregglesRe-titling based on comment #1 and that issue being fixed.. I also feel this is "by design."
At a minimum it's how Drupal has worked for a while and this is the first time I've seen it documented as a problem so downgrading the priority.
Comment #3
sunAbsolutely no idea what the destination query parameter has to do with this issue.
Attached patch fixes the order of nodes. Updated marker not tackled yet.
Contains fragments of #850078: DTBNG Database layer is difficult to debug: Improve instrumentation
Comment #4
sunAttached patch fixes both bugs. Someone up for writing tests?
Comment #5
greggles@sun, the reason the updated marker doesn't get set is because the node/NID/edit page is something like node/2/edit?destination=admin/content and so you never visit the page so the history is never set. You can repeat the behavior with any destination parameter on the node edit screen which is why I stated it in a generic way rather than this specific set of steps.
In my opinion, that's not a bug. You've never seen the page so it should say "updated."
The sort issue is a clear problem and this patch does fix it.
Comment #6
sun#993026: Default sort on admin/content incorrect fixed the TableSort default order, including tests.
Comment #7
gregglesIn my opinion the remaining problem here is not something to fix, but it also seems unlikely to be "major" since this has been present in Drupal for ~4 years.
Comment #8
klausiSo the status is active until we figure out whether this is a bug or intended behavior.
Comment #9
tmsimont CreditAttribution: tmsimont commentedIs there any documentation on how the "new" and "updated" markers are designed to work?