Auto mark-read

[DaveEV]

I use just "View Active Topics" (at the top left), and then look for the "go to first unread" icon-links to identify any topics with new posts.

That way, I can easily read (or skim) all the new posts.

One can easily skip topics if not interested.

That's usually what I do - but it would be nice if there was a "view unread topics" link - that way it's even easier to see threads I haven't fully read yet. Other forums often have this feature.

[wxxyz]

Looks like there's a difference of opinions here....

I most definitely do not have the resources to code a special feature into the forum, but if turbo2ltr can tell me where the toggle in the admin for that option is I'll gladly click it.

[turbo2ltr]

After some research, it seems there is a difference between phpBB 2 and phpBB 3. In 3, they changed the mark-read behavior to "every post is unread until marked read". It is switchable.

Under Load Settings -> General Options:

Enable server-side topic marking: One of the many new features phpBB3 offers is server-side read tracking. This is different from phpBB2, which only offered read tracking based on cookies. To store read/unread status information in the database, as opposed to in a cookie, select Yes.

But it seems most people like it like this, and if everyone is used to it, it's probably better it just stays the way it is.

At least I know why now..

[garygid]

The link going to the "first unread" post in a topic still does NOT go
to the correct post on longer topics. It goes to already-read posts
one or several days earlier.

On most shorter (or more recent?) topics, it sems to work fine!

[DaveEV]

The link going to the "first unread" post in a topic still does NOT go
to the correct post on longer topics. It goes to already-read posts
one or several days earlier.

On most shorter (or more recent?) topics, it sems to work fine!

Yep, I'm seeing that, too. Interestingly - it does seem to work if I'm not too far behind on those longer topics.

[garygid]

I am rarely more than 24 hours behind, but it worked flawlessly before the "upgrade".