Change for change sake, can SUCK.

[MrWild]

It might have seemed like good idea to change the way threads are presented, but what has happened is a cluster fornication. I see a new post has been made to one of the threads I've followed, I click "Last page" go to the bottom pf the page and it ends with an old and dated post. I then look at the "Post Tree" at the top, look through all the branches, waste time hunting, then give up on the Post Tree, and look up the all posts made by the poster, and in that way I find the most current post. (maybe the most current, I'll not know because of the stupid convoluted cluster piddle way threads go now)

Please go back to the old way. This new thing might be new, but it truly sucks.

[ihavenofish]

i didnt notice any change....

[Al_The_Man]

i didnt notice any change....

Me neither?
Al.

[port_huon]

I think MrWild is referring to seeing a screen showing the latest post only with previous posts showing in a scroll down window at the top?

If so, go to User CP and select Options. Under there, look for Number of Posts to Show Per Page. Set this to something other than Forum Default and the problem is fixed.

[ger21]

I think MrWild is referring to seeing a screen showing the latest post only with previous posts showing in a scroll down window at the top?

You're describing what I think is called Hybrid view. Right above number of posts per page. Change to Linear-Oldest First.

[port_huon]

I had the same display and only changed the Number of Posts option.
I already had Oldest Posts first selected.

EDIT: You're right Gerry. It's hybrid mode not Number of Posts. I'm pretty sure I didn't have Hybrid selected at any stage
but I had been logged out for a while which normally doesn't happen so changes could have been made during that time.

[MrWild]

My options are for lineer mode, but i keep getting threaded mode. I have newest first with no cut off, and sometimes the new posts are not displayed. This started on Thursday night after several error screens saying there was a memory overload by your server. I'll try signng out and logging back in and see if that changes things. Might try a cold boot too...