Time stamp fairy

[BOAC]

The DB seems to have gorn 'tits up' again - the AA thread in R&N shows 34 pages plus a 'latest post' by JW411 I cannot see (on its last page 31).

[Shiny side down]

A most entertaining read

I have just read this thread from finish to start, (or somewhere in the middle at the end)

If ever Messrs Pratchet and Adams had collaborated on a novel, this could well be a typical chapter.

[Saab Dastard]

BOAC,

That's not the time stamp fairy, it's the last post / page pixie.

The latter can be cured by changing the number of posts per page you are viewing, apparently.

SD

[BOAC]

That's not the time stamp fairy,

- yes, I know, just being thread lazy (and don't call me a fairy)

Changed the page view from default to 20 - no difference. Went to 30 and all the 'missing' posts appeared but there were still more pages than actually there.

Good luck!

Edit: Back to default and I an still stuck on p31 of 34 with missing later posts.
Edit II: Right chevron shows correct bubble prompt of 'posts 621 to 640 of 670' but I cannot move past 620 on default view

[Saab Dastard]

Interesting - I have no problem seeing that thread (the whole thread and nothing but the thread, so help me...)

Maybe you have to clear your cookies and other downloadable delicacies.

SD

[BOAC]

I have no problem seeing that thread

- this is what happened last time - I was OK then, others were not, now it has swapped.

I cleared all PPR cookies down to do not accept site cookies, still the same. Reinstated 'normal', logged in again, still same. Even at 30 per page now I am stuck on p21 post 630 with pp 22 and 23 'showing' but unviewable.

Almost unbelievably it shows 675 posts on the thread, but 630 is timed at 0630G 14/12?? Can there be 45 more posts in that time?

At 40 per page, p15 shows up to 600 correctly but 16 indicates 601 to 640 but shows only 601 to 630.

The AF447 thread is showing correctly at 805 posts all viewable

[treadigraph]

If it's any help, I'm seeing the same as BOAC on the AA thread; Page 32 is the last visible page, with 33 and 34 allegedly there. Last post 630 on P32 at 6:36am.

I've heard in the past that a false page count can be due to earlier posts having been deleted - dunno if there is any truth in that?

[green granite]

Yep, same problem as BOAC, click on 'last page' and it takes me to 32 but shows 33 & 34 click on either, 32 reloads.

Obviously another good theory as to the cause bites the dust

[Mike-Bracknell]

It's all well and good blaming the timestamp fairy and the last page post pixie, but methinks someone needs to kick the database goblin and the PHP weasel.

[stepwilk]

Yep, same problem as BOAC, click on 'last page' and it takes me to 32 but shows 33 & 34 click on either, 32 reloads.

I -think- this is normal. On many threads, extra pages are preloaded because it's apparent they will be needed, but there's in fact nothing on them yet. As soon as posts spill over onto the next of those "extra pages," you'll be able to access it. The reason you try to open page 33 and 32 reloads is that there's nothing on page 33 yet.

[BOAC]

step - you need to read

"I cleared all PPR cookies down to do not accept site cookies, still the same. Reinstated 'normal', logged in again, still same. Even at 30 per page now I am stuck on p21 post 630 with pp 22 and 23 'showing' but unviewable.

Almost unbelievably it shows 675 posts on the thread, but 630 is timed at 0630G 14/12?? Can there be 45 more posts in that time?

At 40 per page, p15 shows up to 600 correctly but 16 indicates 601 to 640 but shows only 601 to 630."

It was not just about 'pages'.

Anyway, hush hush whisper who dares - just come back to the machine and it is normal!

EDIT: Someone whispered! It is only 'normal' if I come OFF forum default page view..

[BrandiNettIB]

Thanks for the reports, guys. We are looking into this.

Please provide more reports of the issue if/when you see it. What would be helpful would be the time (Z time) at which you see it, a link to the thread in which it occurs, and a screenshot if you can get it.

Thanks!

[BOAC]

Never let it be said we Limeys don't look after you.........................

2155Z

http://www.pprune.org/rumours-news/3...amaica-31.html

Page view at Forum Default

P31 shows '601 to 620 of 640' but cannot access p32 which says '621 to 640 of 640'

[BOAC]

I am convinced it is a result if the VB software not keeping track of editing of threads as someone else has stated. Indeed, since I first reported this here, my post at the top of p31 (default view) is now one back at the bottom of p30. It does seem to be a bug in the SQL update.

[BrandiNettIB]

Thanks, BOAC, for the info. So what happens when try to click on page 32? Do you get an error message? Do you simply stay on page 31? Or do you go to a page 32 that displays nothing?

It's possible that post editing may be related. If a mod, say, deletes five posts quickly, that would reduce the number of total posts and thus potentially affect total pagination. The most visible context for this is, as you observed, posts at the top and bottom of pages. But unless heavy editing is going on, that wouldn't explain page count overages of, say, two or more.

[BOAC]

Just checked again today, Default page view

Do you simply stay on page 31? - yes

But unless heavy editing is going on, that wouldn't explain page count overages of, say, two or more.

- I take it you have not studied the current mod team, then?

On my (php) forums I would not expect this to happen - and if it did, it would not last past the daily DB cycle.

[BrandiNettIB]

Thanks, BOAC. One of the site admins has disabled the option that lets users choose how many posts to view per page, which forces everyone to use the default view. Aside from being easier on the server, that means everyone should be on the same page now in terms of troubleshooting.

If, as you see them, you could link to threads in which you observe the "show more pages than there actually are" issue, that would be helpful. (Please start a new thread, as this one is about time stamp problems.) Thanks!

[BOAC]

New thread started for you.