O
Optimopeach
Guest
I've noticed this problem a lot and it is fairly frustrating. I've never experienced this on any other forum, so I don't know if it is a result of the sheer volume of user traffic or what. Anyways, sometimes when a post is made that requires a new page to be added to the thread it takes a minute to appear.
For example, let's say there's a thread called "Fighter X's new interview."
Posts: 10 (10 posts per page)
User K replies to the thread, bringing the post tally up to 11. Because the default amount of posts displayed per page is 10, a new page is required for the post.
On the main forum page where you can see the list of current threads you will see that there is a new post in the thread by User K. However, when you click the option to be taken to the post, you are instead directed to page 1, as page 2 doesn't exist yet.
Does this make any sense? I'm not the best at explaining things, and I'm hoping someone else has noticed this that can fill in any blanks. Either way, it is insanely annoying, and it lasts anywhere between 30 seconds to 2 minutes from what I've seen.
Hope this helps.
Oh, by the way, it doesn't seem to be browser specific as I've experienced this in both Firefox and IE.
For example, let's say there's a thread called "Fighter X's new interview."
Posts: 10 (10 posts per page)
User K replies to the thread, bringing the post tally up to 11. Because the default amount of posts displayed per page is 10, a new page is required for the post.
On the main forum page where you can see the list of current threads you will see that there is a new post in the thread by User K. However, when you click the option to be taken to the post, you are instead directed to page 1, as page 2 doesn't exist yet.
Does this make any sense? I'm not the best at explaining things, and I'm hoping someone else has noticed this that can fill in any blanks. Either way, it is insanely annoying, and it lasts anywhere between 30 seconds to 2 minutes from what I've seen.
Hope this helps.
Oh, by the way, it doesn't seem to be browser specific as I've experienced this in both Firefox and IE.