FAO Miguel: 'Glitches' noticed after March 2011 Server Change
Joined: May 2009
Posts: 611
Likes: 62
From: Down under
No, it's broken. I see the same symptoms as Machaca. It shows a false last page number at the top, but the thread is still active on the previous (and valid) last page.
FOR
FOR
Last edited by FullOppositeRudder; 21st March 2011 at 06:11. Reason: Test
Joined: Jan 2008
Posts: 798
Likes: 0
From: The Land of Beer and Chocolate
It's gotten better. Now you click on the thread and you see page 98 for a second or two before it redirects you to a thread in spotter's corner about how the aircraft is to be displayed in a museum......
Joined: Jul 2007
Posts: 377
Likes: 0
From: My Stringy Brane
I can view as far as http://www.pprune.org/rumours-news/3...er-nyc-98.html
Selecting page 99, 100 or 101 redirects back to page 98.
Selecting page 99, 100 or 101 redirects back to page 98.
inactive
Joined: Apr 2008
Posts: 383
Likes: 0
From: US
Sorry, I've gotten a bit confused and I'm not familiar with how long the Hudson thread was previously?
Do we know for sure that there should have been a page 99 or 100? I see the last post on page 98 is March 23 (today).
Sometimes there are caching issues that could cause an extra number to show up temporarily after a solo post is deleted, but that should clear after the next post.
Are there other examples of threads that have known additional pages that aren't appearing?
thanks everyone for your input here, it's been helpful as we fix the niggling bugs.
Do we know for sure that there should have been a page 99 or 100? I see the last post on page 98 is March 23 (today).
Sometimes there are caching issues that could cause an extra number to show up temporarily after a solo post is deleted, but that should clear after the next post.
Are there other examples of threads that have known additional pages that aren't appearing?
thanks everyone for your input here, it's been helpful as we fix the niggling bugs.
More bang for your buck
Joined: Nov 2005
Posts: 3,513
Likes: 1
From: land of the clanger
MiguelIB
I suspect it possibly happens if a MOD tidies up a thread and deletes more than a page full of posts It has always done this on rare occasions but since the upgrade it has come much more frequent. Once of course there are sufficient number of posts to fill up the empy pages then the problem dissapears. Hope this helps
Also currently http://www.pprune.org/rumours-news/3...er-nyc-98.html
I suspect it possibly happens if a MOD tidies up a thread and deletes more than a page full of posts It has always done this on rare occasions but since the upgrade it has come much more frequent. Once of course there are sufficient number of posts to fill up the empy pages then the problem dissapears. Hope this helps
Also currently http://www.pprune.org/rumours-news/3...er-nyc-98.html
inactive
Joined: Apr 2008
Posts: 383
Likes: 0
From: US
ZFT - We're going to be doing some hardware updates in the next couple weeks as well which we think will alleviate most of these types of messages. Luckily (and sometimes unluckily) PPRuNe is a really big forum with a lot of traffic and so we do sometimes see conflicts occur when hitting a page.
Green Granite - thanks for that information. We're continuing to investigate this.
Green Granite - thanks for that information. We're continuing to investigate this.
Joined: Jan 2008
Posts: 1,133
Likes: 0
From: Bracknell, Berks, UK
Miguel,
When I posted about the Hudson River thread, the thread was 101 pages long (apparently), and page 98 didn't contain the final post. I had only noticed it as the thread had recently come back to the top of the pile due to someone posting something on it - yet I couldn't read it as it was 3 pages past the limit of where I could access. I think there's probably some dodgy indexing of thread posts going on in the database?
When I posted about the Hudson River thread, the thread was 101 pages long (apparently), and page 98 didn't contain the final post. I had only noticed it as the thread had recently come back to the top of the pile due to someone posting something on it - yet I couldn't read it as it was 3 pages past the limit of where I could access. I think there's probably some dodgy indexing of thread posts going on in the database?
