Subscriptions acting funky

[Superorb]

This is a question mostly for the admin or someone else who has access to the Admin panel.

I have a problem where when I click on the "take me to the first unread post" from my UserCP it does not take me to the first unread post. It always missed a ton of new posts and I have to scroll up to find a post I've already read and then go down from there. It's a total PITA. I also run a vB4.2 forum and don't have this problem on mine. You can PM me if you want to discuss it privately. The following setting is what should cause this. There's 3 options here, mine is set to the first one.

Admin CP -> vBulletin Options -> General Settings -> Thread/Forum Read Marking Type

[Irving]

I have a similar issue with my mobile devices, but I attribute it to the mobile device more than I do the site.

[J]

Ill take a look. I know one option is DB driven and another cookie driven. I suspect you are running DB on yours, as it should be more reliable across devices and sessions, but use more resources on te server.

Ill see what we are set at, and we can test the load impact here for a bit with this change.

[J]

This forum is set to the first one as well, which is session based inactivity timeout. One difference we might have is that our inactivity timeout is large to accommodate a few devices our members use. I'll try the automatic marking stored in DB, which should give the most accurate results, but is most draining on server resources. If it seems to have a bad impact on performance, I'll switch it back.

[Superorb]

Weird, now I have to scroll down past the threads I've already read to get to the new ones.

For example this thread. I've read half the thread but when I clicked the "take me to first unread post" it took me to the OP, first post. This little marker at the top left of the thread is light blue so it thinks I haven't read it yet. I'll let it be for a while and see if it fixes itself. vB will flush caches on its own so fingers crossed it works

[Superorb]

This forum is set to the first one as well, which is session based inactivity timeout. One difference we might have is that our inactivity timeout is large to accommodate a few devices our members use. I'll try the automatic marking stored in DB, which should give the most accurate results, but is most draining on server resources. If it seems to have a bad impact on performance, I'll switch it back.

How long is the timeout? Oh, and please turn on automerge doublepost.

[Superorb]

I don't know what option you chose but it seems to be doing much, much better for me. Have you noticed any increased load on the server?

[J]

The DB tracking caused some changes that some of our members didn't like. Switched it back, but cut session timeout to a more reasonable length. It was up on purpose due to some issues we had from a leased server at our last host. Seems ok lower now that we are on a better platform.

[brutal]

The DB tracking caused some changes that some of our members didn't like. Switched it back, but cut session timeout to a more reasonable length. It was up on purpose due to some issues we had from a leased server at our last host. Seems ok lower now that we are on a better platform.

I thought I noticed a reset of last read of sorts when you were doing this.

[brutal]

Go to "First new post" is not working for me today. Goes right to the end.