FOG 1.6-working - retaining history order
-
When loading a Host Login History (or other data sorted by time/date), FOG 1.6 defaults to oldest first. Whilst this can be sorted, when the page is reloaded it returns to oldest first.
Newest first (or a set user preference) would be more useful (certainly for login history). No urgency for this feature.
-
@sideone 3007ee9f2 shoudl do that (latest commit.)
-
@Tom-Elliott thanks - is there a setting that has to be changed? It doesn’t save it automatically.
-
@sideone You may have to hard refresh your screen for it to take effect, though it’s also possible what I added just simply didn’t work. Didn’t have a chance to test it for myself. Only just got my dev system slightly back up (and am typing to you right now from it.)
I’m pretty sure it’s the hard refresh issue though.
Try CTRL+SHIFT+R in Google Chrome. (I know, I know, F5 or the refresh button should do it) but it doesn’t. Hard refreshes clear all local app cache for JS in browsers and is a specialized step for the procedure.
-
@Tom-Elliott Tried Ctrl-Shift-R but settings not retaining the search order, I’m afraid.
-
@sideone Please retry the latest yet again. It seems the changes I made before just didn’t take or were accidentally overwritten from another commit.
-
@Tom-Elliott Looks like its working now, thank you!
