This just started happening a few days ago, and it just happened again.
Discourse showed that I had two unread topics. I clicked on the ‘unread topics’ link and it brought up the two threads. I opened one thread, read it, and then opened the other thread and read it.
Then Discourse showed that I had 1 unread topic. When I clicked on that message, it said I had no unread topics.
If I refresh the page instead of clicking the link, the ‘1 unread topic’ message goes away.
What do you refresh and how does i clear anything up? I tried clearing the page I’m on, the note that says I have one unread, the reply that says there’s no unread. None of those clears anything up. The reply is still that there are no unread and the next time when I’m told there is 1 unread, there is still no unread. This just started, so surely someone can figure out what they did to cause it and fix it.
This is where you need to refresh. You can do this:
Or, in Chrome, I can either click the circular arrow to the left of the address bar to refresh, or I can right-click anywhere on the page and select ‘Refresh’, or I can do Cntrl-R.
Once you refresh, the ‘1 Unread’ message goes away.
But, dammit, it’s been a couple of weeks. FIX THIS!!
Apparently we are not important enough to get any help with this. The problem began only a short while ago and clearly is because of something the folks at Discourse DID. One assumes they keep track of things they do (maybe a rash assumption?) so it ought to be easy enough to FIX IT. Ok? Is anyone out there???
VERY annoying. Why can’t this get fixed? Why can’t someone explain why if there is a reason? It’s so stupid. If you can’t figure out how to fix it then turn off the stupid “unread count” feature altogether so we won’t be continuously looking at a mistake.
.
I obviously am also still experiencing it–in Chrome on both my Windows computers (Win 10 and Win 11), Samsung Android, and–just verified–Edge on my Windows 10 laptop.
I just had that happen to me. Win10, Edge. The post that it thought was unread was one I’d just added the latest post to.
I went around between that thread and the unread[1] page a couple times with no change.
Then I pulled up the thread, pressed Ctrl-F5 for “force reload the whole page”, and the problem disappeared. Unread now recognized that I’d seen that thread through to the end.
I’m suspecting it’s an interaction between the browser’s cached page and Discourse’s complicated behind-the-scenes updating engine.
So anyone suffering from this might try that: pull up the thread that Discourse mistakenly thinks is unread for you, then Ctrl-F5 (or force refresh) and see if that makes the problem go away.