Describe the bug
The sorting is wrong with the new version. It should see the newest first. You see the old one first.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The newest should be seen first.
Screenshots


Server (please complete the following information):
Desktop (please complete the following information):
Additional context
馃憢 Thanks for opening your first issue here! If you're reporting a 馃悶 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.
I have noticed that. I don鈥檛 yet have an explanation for it. The query we do Is pretty straightforward, but it seems latest versions of the JS library may disagree. We鈥檙e on it. I still don鈥檛 know why it鈥檚 happening, but I can reproduce it.
Same for me and for the demo.. but on the "view all" page its sorted correctly.
@jovibroz Yeah, I can see it too - what's bizarre is that those two screens use the exact same API call, and if you call just via API, it sorts as expected. It's a head-scratcher.
@inietov FYI, the CH for this is 15305
I'm glad I'm just a sound engineer with the required computer skills to keep a workstation (and a few ubuntu servers) runnin! :) I'd stay up all night, every night to fix those kinda things if only I knew how :)
10 PRINT "YO!"
20 GOTO 10
RUN
Hah, that's pretty much what it looks like on our end, too :D
\Log::debug('IS THE SKY EVEN BLUE WTF');
We did update the bootstrap-tables javascript, but the weird part is that it was updated everywhere, so I'd expect to see at least consistent behavior. I know in the past I've tried adding the normal table headers (the reload, export, etc) and it seemed to fix it, but that kind doesn't make any sense either (and I really didn't want to jank up the UI with those elements on the dashboard.)
Awesome fix in 5.04. Just a notice that the backups flipped order with this one :)
Huh. I didn鈥檛 even do anything with backups in that release.