Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Cannot mark as read one of my watched threads [MERGED]
- Thread starter UliBaer
- Start date
- Sort by reaction score
Not yet for me. I just marked these as read and when I return, they are unread again.
Still seeing it.
Marked all these (and a few more) as Read yesterday at my home Mac, and now - after a page refresh, mind you - they are unread on my work Mac.
Marked all these (and a few more) as Read yesterday at my home Mac, and now - after a page refresh, mind you - they are unread on my work Mac.
Behavior I am seeing is if I read all my unread threads and go back to any other page, and then return to the Watched Threads page, several will be unread again. I click or tap on the Watched Threads link and they will all revert back to a read status. If I click or tap on the Watched Threads link a second time, then those same several threads will become unread again.
It's like a switch to alternate between two states.
Perhaps MacRumors is experimenting with the quantum and trying to make threads appear in a superposition - read and unread at the same time! hahaha
It's like a switch to alternate between two states.
Perhaps MacRumors is experimenting with the quantum and trying to make threads appear in a superposition - read and unread at the same time! hahaha
In one case, all I had to do was read the problematic thread, and its Read state started working properly.
In another case, it didn't, so I used the forum-level "Mark Read" button. That caused all the threads in that forum to be marked as read, and now I'm waiting for another post in the one problematic thread to see if it's fixed or still broken.
In another case, it didn't, so I used the forum-level "Mark Read" button. That caused all the threads in that forum to be marked as read, and now I'm waiting for another post in the one problematic thread to see if it's fixed or still broken.
Still broken for me. This has been mentioned earlier, but just to recap:
- Reading or marking a stuck thread as read does not work.
- Marking a forum section as read does work, but only temporarily. The thread becomes stuck again when there's a new post.
- If a stuck thread has had no postings for 30 days, then it's marked as read and falls of my unread list. (The forum software automatically marks all posts older than 30 days as read.) However, the thread becomes stuck again when there's a new post.
Last edited:
I've now confirmed this is still broken, despite it somehow being fixed for one specific thread that raised my hopes.
There were two other threads that were previously stuck, and the traffic in them varies, so I had to wait for someone to post in them. Now that's happened, and both threads are stuck.
There were two other threads that were previously stuck, and the traffic in them varies, so I had to wait for someone to post in them. Now that's happened, and both threads are stuck.
I have two stuck in this broken state. Nothing I do will keep them from being marked Unread on future visits.
Possibly fixed my issue? We shall see.
Possibly fixed my issue? We shall see.
Last edited:
No, it's a temporary fix until someone posts in one of the threads again. Then it happens again, and you have to 'fix' it the same way again.
I think it might be getting worse. Now threads that have usually been cleared are not being cleared. I wonder if it has anything to do with posting photos or screenshots in a thread. I know the "Post Your Homescreen" thread is loaded with images and even when you open it, it is slow to load.
I am not sure if this helps, but whenever this happens to me, it only occurs in threads that have been dormant for a while before someone posts a new reply. It's currently happening in three threads for me:
1) Last Post March 28, then someone posted today
2) Last Post March 29, then someone posted Sunday
3) Last Post April 10, then someone posted June 4
In every instance everything was working as expected until the most recent post, and the issue started up immediately.
1) Last Post March 28, then someone posted today
2) Last Post March 29, then someone posted Sunday
3) Last Post April 10, then someone posted June 4
In every instance everything was working as expected until the most recent post, and the issue started up immediately.
I don't have an excuse for this... but I only just now thought to look for a thread discussing such a bug. 
Clearly, I should have sought this out much sooner. Ah well... I'm here now.
I've had one thread which has refused to toggle to read for several weeks now, and just recently another thread joined it in the "forever unread" club. The two threads in question are Do you use a case on your iPhone? [MERGED] and UK Court Rejects Government Secrecy in Apple's Fight Against Backdoor Request, respectively.
Clearly, I should have sought this out much sooner. Ah well... I'm here now.I've had one thread which has refused to toggle to read for several weeks now, and just recently another thread joined it in the "forever unread" club. The two threads in question are Do you use a case on your iPhone? [MERGED] and UK Court Rejects Government Secrecy in Apple's Fight Against Backdoor Request, respectively.
Right now this thread is stuck again for me:
I think you pinged him already 3 times in this thread, you must be on his ignore list
How difficult can this problem be to investigate or solve? MacRumors uses XenForo. XenForo uses MySQL.
Query the database to discover why a thread is seen as unread.
Use a database command to mark the thread as read.
Verify.
Maybe the database is corrupted? Duplicate IDs? That should be easy to discover.
I think I have 11 threads stuck.
Query the database to discover why a thread is seen as unread.
Use a database command to mark the thread as read.
Verify.
Maybe the database is corrupted? Duplicate IDs? That should be easy to discover.
I think I have 11 threads stuck.