I am guessing they using something along the lines of 'last read message #+display value'. With the last message read there is no next message to display. So blank page. With Newest first that wouldn't apply. So you see the correct message.

A work around seems to be selecting "highest rated posts first". With the rating system disabled posts are sorted by oldest first & "Jump to first new post in thread automatically" is still followed.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Thanks to all of you for researching this. How quickly it appears you have, as a team, diagnosed the problem!

Now that there are 76 posts, I can see all 75 on page 1 and #76 on page 2.

I would also like to add my response to several questions that were brought up. First, I had the problem both with Firefox 16.0.1 and two different versions of Firefox's Nightly 64-bit test browsers. I also tried reloading the page outside of the cache, to no avail. When the 75th post was added three days ago, I was able to see it without any problems. It wasn't until I checked again today that everything disappeared. As to Google Chrome, unfortunately the 76th post was added for testing before I could check Chrome's response. As far as the sort goes, I tried all available sorts in Firefox Nightly, and I had the same problem with all. To the question about appearance, the page appeared perfect, nothing missing or out of the ordinary...except for the posts, that is. lol

From your great response I suspect it will be easy for them to find the bug and fix it now. Once again, super job everyone!

p.s. If I missed any questions aimed at me, I apologize.

Should we propose a new forum rule: "every thread must have a prime number of posts at all times"? ;)

As long as you add "... and no-one should be able to set their posts-per-page to any prime number." :-0!

---

Should be fixed now.
-- David

Thank you, David! :)