Issue has been bumped up in tech queue.

Thanks

Paul

The problem is not fully resolved, but some days are better than others. I seem to notice the biggest problem in mega-threads, some of which bump me back an entire month to posts on April 2nd!

Thanks for taking note of this issue, I'll be glad when FT is back and functioning again.

I rejoiced too soon. This evening, clicking on the "go to last post" button of the "Trick It" thread, it took me to post16189995 - a post from April 9th.

I went to another machine and clicked the same button and it took me to post16318698 - which was indeed the first new post for me.

Both machines are running Windows 7 Professional with IE9. They are at different locations on different networks.

Now, so long as I didn't click the "Mark this forum read" option, closing and returning to the thread in fresh browsers consistently returned me to the same two posts on the two machines (the April post on the one machine and the first new post on the other machine).

what's funny is that I have the problem with this thread now.

LOL you're right! Took me to post #16. I posted #18 so obviously #16 couldn't be "new" to me.

I realize now that this happens not only with my subscribed topics. Originally I noticed it only with the subscribed topics in "My Flyertalk" but I understand now it will happen in many topics with new posts, even if I have not subscribed to that topic.

I'm really looking forward to getting this resolved.

This problem is occuring for me as well.

+1

Will anything be done about this?

Will the situation be improved with opening a new account?

This is an ongoing issue of which tech has been aware for some time; creating a new account (?) will not remedy this (and is against the TOS anyway).

I'll update when I have new info, but for now this issue is outstanding.

Paul

Just a data point: one of the computers I now use to access FT has only IE8, and I have noticed this issue when using that computer.

The other computers I use to access FT have Firefox and Chrome, and I do not notice the problem on those computers.

The issue appears unique to IE.

I am using IE9. I never had the problem before I upgraded to IE9.

The fact that nobody from FT has bothered to ask us anything about our problem and configuration makes me think that so far nobody has even bothered to start working on our issue...

If this problem persists much longer I think I'll need to setup a second temporary account and see if I have the same problem with that account.

While I use IE7, IE8, IE9, and Chrome on a variety of PCs, and the default browser on Android 2.2.2, it may be that the problem never appeared until I used IE9. However, for me, once a particular thread has the problem, it persists across all browsers. For me, it is not dependant on subscribing to the thread or not.

This seems clear. :confused:
If the problem is IE9 related, then at least we will start to see a large percentage of the users encounter this problem as it is starting to be rolled-out through automatic update.

It seems that something has occured on this topic. Either I have been very luckly today to not hit any of my "broken" threads, or my last viewed counters were all moved forward, or this topic has been fixed. (I hope :) )

For others following this thread, what is your experience today?

I'm using IE9, and as of yesterday evening, I was still having this problem.