135 unread in Tumbleweed?? No way - I stay current.
So I click on Unread (135) link.
At the far upper right, there is a Dismiss link.
I clicked it and a pop up shows up (see it below)
So I put a check-mark in the “Stop tracking …” and click Dismiss button.
There are still 135 Unread. I’ve logged out and back in, still the same.
No doubt because of the recent changes to the Forum Software, this issue was introduced … (this Unread(135) wasn’t there an hour ago … only after I saw the Forum changes had taken affect, this is my side effect):
(Upcoming Forum Changes
On March 17, we’ll be implementing two changes in the forum’s technical categories.
First, we’re enabling the “auto close topics” functionality to close inactive topics.
…
Secondly, we’re implementing a frequently-requested feature to mark a response as a solution.)
I click “Unread (135)”, then continually click the scrollbar down to the end, then tap that Dismiss at the bottom right, select Dismiss all, then the Dismiss button - same thing - does not clear out the count.
Odd that the Unread ranges from May 2023 to Dec 2023.
If I click on each Unread thread, the count does decrease (130 now) one at a time.
Anyway, thanks for the quick response - no biggie for now, I will just ignore it and pay attention to threads that are in bold. (i.e., Unread). We can close this now
Sounds good. I’m doing some investigating in a sandbox environment to see if I can determine what’s going on and why it’s not clearing for you. I think that if you select the checkbox to stop tracking, that doesn’t clear it - so it may be that you need to leave that unchecked when dismissing, but I’ll see if I can verify that.
ETA: It didn’t seem to matter whether I checked the box or not, the unreads were marked as read in my quick testing. I may take a look at your account here further if it doesn’t clear for you in the next day or two.
Initially had the same problem. But after scrolling down in the list of unread messages (some 1000) with the scrollbar on the side (only some 100) and going up again, the dismiss button on top worked.
You mis-read my recent reply … I DID scroll all the way to the very bottom of the replies and there IS a Dismiss button at the bottom (I did not scroll back up).
And you misread mine. After scrolling up again, the upper dismiss button worked. I didn’t have the time to scroll down several thousands of threads, so only scrolled down a few 100.
I had a look at your account, and I’m not sure why it didn’t clear when you were in the English category, but I noticed that the same count of unread messages was visible from the overview of all categories, and I was able to clear it for you from there. Should be good now.
I also have this problem. I only have 30 odd posts so I am going through them manually. So far they are all posts that have a single new message saying they have been closed.
Thanks for the report. The system message that the topic was closed is treated as a new message for notification purposes, it seems. Doesn’t seem to be happening for everyone, but it is odd that it’s showing at all.
It’s not auto-closed topics that triggered the notifications. I was unclear in my explanation because I didn’t differentiate between the two related processes that run in order to bring things to a consistent state in the message database.
It’s the (automated) manual closure of topics that would have been auto-closed had the option been configured previously.
The application of the changes involved running an automated process (once the configuration changes were made) that did two things:
Updated all topics with an auto-close timer setting so that, if there’s no further activity, they will be automatically closed after 30 days of inactivity from the last post.
Manually closing all topics (via a built-in ruby task) where the 30 days of inactivity had already passed.
It’s the second part that triggered it. The automatic close does not send a notification when the automatic timer essentially ‘expires’ the topic and closes it.
I confirmed this in my test environment previously.
