Page 1 of 1

"Mark as Read" to specific boards not working

Posted: Mon Sep 05, 2005 10:46 am
by chette
1. I click a board, and select mark as read
2. Then I go to Recent Unread Topics, and I still see the posts in the boards that I "marked"

Just me?

Re: "Mark as Read" to specific boards not working

Posted: Mon Sep 05, 2005 4:34 pm
by [Unknown]
Are you sure of all of the following?

[*]The page you're going to is not cached.  Try pressing F5.
[*]The topics you are seeing weren't posted since you marked the board as read.
[*]You are marking the correct board as read (it does not effect child boards.)

-[Unknown]

Re: "Mark as Read" to specific boards not working

Posted: Wed Jun 28, 2006 11:35 am
by Eelke
Sorry to dig up an old thread, but I have this same problem, and I am positive that
  • The topics I am seeing weren't posted since I marked the board as read.
  • I am marking the correct board as read
As for the page being cached, at least pressing refresh (Firefox 1.5) doesn't make any difference, so if it is being cached, refreshing doesn't change anything about it.

Oh, one other importan aspect: often when I visit the same board a bit later in my session, it is marked as unread. So, it does seem to work eventually, which does suggest caching someplace or other, just have no idea where to look.

Re: "Mark as Read" to specific boards not working

Posted: Tue Jul 04, 2006 8:43 am
by Eelke
It seems like it has something to do with caching somewhere or other (do note that I use other forums that do not have any cachning problems, maybe HTTP-header controlling the caching behaviour on here). The reason I say this is because I also not see my own posts for some time after posting. After one or two page refreshes they suddenly show up.

Re: "Mark as Read" to specific boards not working

Posted: Tue Jul 04, 2006 9:49 am
by Eelke
When investigating another problem I found this doesn't occur on another installation of Firefox 1.5.0.4 either (different machine, same network; occurs on a machine of the company, doesn't occur on my own laptop hooked onto the same network).

In that case, it seems such a specific problem that it isn't really worth the effort, maybe this information is of any use to someone running into the same problem.