Good spot! However, most of the dropdown timeframes end with yesterdayâs date. But âall timeâ does not. And amongst those users that are listed are those who joined X hours ago, where X is less than the current hours into today.
Given that this has come up three times on meta (Iâm fairly confident it has), I wonder if we should put some kind of disclaimer on the page â either for staff only, or for everyone â about the daily refresh.
I donât think we send the âlast updated atâ details to the client, but if we did, I think thereâs some benefit to displaying that information to both users and staff. We can tone it down a bit and make sure itâs placed somewhere where it canât be missed, like right underneath the period select-kit.
I like this idea very much, can we assign it Monday @eviltrout? I assume itâs fairly easy based on what Iâve seen in the mocks? Iâd like the reduced tech supportâŚ
Thanks @Stephen ⌠but five hours after your post here I still canât see either of them at /u in my desktop browser, a fresh desktop browser, or in my phoneâs browser. Weird.
Correct number of registered users I have from the About page
Due to this, I have to disable user directory so it doesnât look like a kind of fraud on my part when users visit users all time directory and only five users show up.
I couldnât get it to look exactly as tight as @Johaniâs mockups because the period chooser has some built in vertical size but I got reasonably close:
@sheldrake. Yes, it is a bug. And my Discourse instance is very up to date. Iâm on the latest version 2.5 beta 2. I noticed that since August last year but just resorted to hiding users directory since I donât even want same to be available for viewing by others.
Have you verified that even in safe mode it only shows an incomplete count? I would do that and try disabling all plugins, it needs to occur with zero additional code to be something we can readily troubleshoot.
A bug would be something affecting all instances of Discourse. Yours is the only one Iâm aware of that exhibits this. If it began in August last year it may be a plugin or other customization thatâs responsible.