Quote Originally Posted by Togakure View Post
This is minor in context, but it has annoyed me for some time now. The "mark forum read" function doesn't seem to work consistently throughout the board. I don't know if this is skin-related or not (I use the earthy-colored "Guild" skin).

At least one forum works as the function should (I can't remember which one specifically at the moment): there is immediate visual feedback on the thread list, where all unread threads are marked read, without requiring a refresh. A great many forums do not work this way.

Hopefully this isn't skin-related, as multiple skins would multiply testing and fixing. I suggest trying this function on each forum and sub-forum, starting with the Guild skin since I know that the problem occurs with it, and noting which work as expected and which do not, then noting the settings of one that works correctly, and setting all the other fora up the same way.

I'll edit this post with information about which forums seem to work as expected and which do not, with more details, later.

EDIT1: example, the Front Room. I select Mark Forum Read and click, and nothing happens. The drop-down remains. If I then back out of the FR and return, the threads still seem unread. If I then refresh the browser, they all are marked read.

Iirc, the Watchtower works properly, but I need to confirm this and there are no unread threads for me in here at the moment.

EDIT2: The forums that work correctly are the new TWS2 forums. When I select "mark forum read," the drop-down list clears, and all the unread threads instantly lose their bold text, without me having to click my browser's refresh button. Many of the older forums do not work this way.
I have investigated this, and found the cause. It is not skin-related. It happens in any forum that has a subforum. If you click Mark Read from the Forum Tools, the threads DO get marked read, but the page does not reload so you do not see the unread icons disappear. If you manually hit reload, they will shift over to read icons (as they will if you browse away and come back). A bit of research indicates this may be caused by a conflict with another plugin. I will try and figure out what is causing it, but in the meantime just manually hit refresh after clicking the button and it will work.