My unread menu section shows the wrong value (2)

The unread menu topic shows (2) as unread. When clicking on the link it says nothing left.

On the second picture it mentions that, :information_source: You can view and change your new topic tracking settings in your preferences. I was trying to do some changes, however when refreshing the page, the (2) is back.

Am I alone with that?

I can work and live with that, however it indicates and re-forces the wish to have a test environment to implement changes.


People over on https://discuss.kde.org/ complained about the same issue a few weeks ago.

Usually the count comes good after a bit of reading post.
Especially following the links in the menu for repies and likes.

I checked on kde’s discourse site, could not find anything. However I do have a progress…

It shows now (3) unread and still get the nothing to read message :smiley:

This is starting to be really annoying, as it makes me miss responses to threads I’m tracking.

I see “Unread (2)”, click on it, and that apparently immediately pushes those two topics with unread messages out of the queue.

The original post of ilikelinux looks to me as if the (2) is a wrong value whereas the correct value would be then (0). So my first assumption would be that there were no actual messages (given that the (2) returned soon later). Do you have indication that there were (2) actual messages that had been accidentally dismissed in your case?


I can currently not reproduce this. I will have another look tomorrow. Feel free everybody to add data/elaboration. If you use stuff like ublock or noscript, it might be also worth to test without to see if that is related to the issue.

In any case, users who have this issue, please let us know if so (a short post here suffices), even if you cannot add data!

At the worst, if there is really a bug that causes dismissals or so, we might open a support ticket with the super powers of our enterprise subscription :classic_smiley: So no panic :classic_smiley:

I think so. I’ve now found threads that had (1) indicators next to them in the “Latest” view, but they’re not showing up in the “Unread” view. Or maybe I’m just holding it wrong?

At least I got a new “Unread” entry for your response above, so it seems to be working ~sometimes~

As I said, making changes on the live system is the worst thing what we can do. Especially when we are different groups tinker on it. We will never have the overview and everyone can say it was not me. And we do have to believe it, if we want or not :man_shrugging:

I got six new unread messages while I can extract two of them as not available.

Yeah, it’s comparable to technical debt that was created over time, but I think the problem is not only the undocumented/uncoordinated changes but also that Discourse has become very complex and thus creates a flat learning curve…

I much appreciate the work @kevin has started to dig into our configuration in order to learn understanding & documenting it over time, but I think Discourse is too complex to do this overnight :frowning: I hope the site admin repo will be used more actively in future by other site admins too when doing any actions to keep documented what is done and how to reproduce it. There is hope, but it needs time :classic_smiley:

test. ignore this post.

this is a test

I just try to be sure that I get everything right: You mean the blue circle with the number in it immediately right of the topic title? And when this was shown with the number 1 on a topic, “unread” was not shown (=0) at the top, and you did NOT open the topic but clicked on “unread” and the unread was still empty?

One thing I currently wonder is if the “latest … active … new … unread … bookmarks” line at the top is maybe not refreshed always when the “Latest” list of topics is refreshed. That could explain, e.g., that “unread” does not change if Discourse only refreshes the “Latest” list of topics below (adding new unread topics) when clicking “See 1 new or updated topic”.

It might be worth in such a situation to test to refresh the whole page with F5 or so, to see if it makes a difference to refresh the whole page. It would be good to know more when/how it behaves in your case.

Is there a possibility to provide screenshots? Maybe also of subsequent steps/pages.

Do you have modifications of your firefox?


I still cannot reproduce it. When Benjamin made his post, my Discourse main page was immediately updated with the one “unread”. When clicking the “See 1 new or updated topic”, I saw the topic with the blue circle plus the “unread” above. Clicking on the “unread”, I get a list containing this topic with his unread post. It remains that way until I opened this topic at any page/tab. It would be good to understand when/what behaves different.

It is entirely possible that I’m just holding it wrong.

But I definitely get the “Unread (2)” (or different numbers) and then seeing zero unread topics when actually clicking on it. Not sure if it’s making me miss unread responses to topics I’m tracking or not.

I also meant I cannot reproduce the “Unread (2)”, but as far as it looks and as far as I see the screenshots, this is likely a bug. And with you, we have more than 1 user able to reproduce it.

The open question remains only if it’s just a wrong value in the headline, or if it really dismisses messages.

I will have another look to see if we can do something about it, but if not, I have a tendency to ask for opening a ticket at the Discourse support. We have a bug, so that justifies it. And then they can see what’s the origin and if there is a chance that messages are dismissed.

I keep you posted.

Everyone feel free to add information, elaboration, screenshots, etc. → including information about who experiences it (the number of affected users matters, and maybe their technical circumstances).

Especially a second case with screenshots of the different screens would be useful. E.g., a “latest” list that has more blue circles (tracked+unread) than the top “unread” category, or both an “unread (2)” screenshot with subsequently another screenshot of the still empty “unread” category once it is clicked to be opened.

I have this problem as well, but for me there is 1 unread message ghost that shows up from time to time.

I’ve had this problem for about 3 weeks. IIRC, it first showed up when I had 1 unread message in my queue that, rather than opening, I clicked the “dismiss message(s)” (or however that is worded, I don’t remember exactly). When I dismissed the 1 message without opening it (but I had previously been following that thread), I also checked the “stop tracking this conversation” box (again, I forget the exact wording). The problem didn’t immediately show up, but I think it surfaced after I had closed my browser tab (and maybe opened this discourse site on another PC). Ever since, on and off, I get that ghost “1 unread message” notice, which I assume is the conversation that tried to dismiss and unfollow without opening.

HTH :slightly_smiling_face:

I wonder if this is an issue with cookies or a backend issue?

I’m not seeing the unread count being wrong - and I’m on three discussion forums. Also I’m reading on three OS, macOS+Firefox, Fedora+Firefox and iPAD+Safari.

Maybe one people seeing the problem could try clearing cookies?

I opened a new private window and logged in there. That would mean that the cache is empty, right?

This we should have done already, If it is a known issue from discourse upstream we can stop assuming!

I bet it has something todo with this:

I have noticed this a few times recently (seeing an unread count, but there are none), but I put this down to me leaving a tab open at one discussion, then reading another in a new tab, then coming back and noticing that the earlier tab showed the notification, but I had actually read the posts elsewhere.
I’m not saying this is the case for everyone of course - there may well be a bug, I do this quite often but only noticed this behaviour fairly recently.

Ok folks, I asked if it is possible to open a ticket at the Discourse support to take care of this. I have limited time to invest this week, and I think I cannot do much more anyway. Based on the feedback of several experienced users here, there is very likely a bug that manifests in the “unread”. We don’t know if the implications are just the “ghost” numbers or if there is also the dismissal of messages, but in any case, its a bug, and that is worth a ticket. Just to be sure :classic_smiley:

Maybe a site admin will prefer to try themselves first. They have also means exceeding mine. In both cases, give them some time to work on this :classic_smiley:

Please keep following this topic: if questions come up, they might ask you to test something or so. Thanks :classic_smiley:

In firefox and in chromium I see an unread count of 4, when I select unread it shows 2 posts.

In firefox I cleared cookies and sitedata for fedoraproject.org and I’m still observing the same thing.