I am loosing customers like flies because of this feature. I need it turned off. I am extremely unhappy that it was not configurable in the admin section. You should never force a feature on to a customer like this.

How can I turn off the "jump to first unread post" .. I want it to act like it did before in the 6.4 versions. When I click on a topic that I have a new reply in, I want it to show me the original post... not the new reply. All of my users find this new feature extremely annoying and I have to agree with them.

Please tell me how to turn it off or create an addition to the admin console that allows me to turn it off.

Actually, we didn't change anything in this area for the final 6.5 release. It works just as it did in 6.4 and earlier. In fact all versions of .threads ever released have always taken you to the first unread post in a thread. To turn that off you'd need to do a code modification which you'll probably find some help on over at threadsdev.com.

In 6.4 If I clicked on a post that I have already read and someone made a new reply to it would show me the original post NOT the new reply, in 6.5 it shows me the new reply first. If you need to see this I can point you to an example but this has NEVER happened before I just upgraded to 6.5 and I have been running Threads for a VERY long time.

Actually - one or two of the 6.4 versions had a bug where the jumper wasn't working right. What Rick describes is how it was supposed to work. But it was broken for a bit a few versions ago.

Can it be broken again? Again, I have never seen it do this before and I have ran every version of Threads even back when it was called wwwthreads and none of the versions I have ran have ever done this.

Josh is correct that the post jumper was broken in a couple versions. Like I said, if you want it to work that way you'll need to check over at threadsdev. I know you've been running .threads for a very long time but I've been coding .threads for a very long time and trust me, the current behaviour is the way it's designed to work You can look in the bugs forum and see the complaints for the couple of versions 6.4.x where it wasn't working properly.

Thank you for the information, I have posted the request over at threadsdev.com ... I just would hate to have to switch boards because of this since I have been using this for so long. Hopefully someone there can help.