The Site > DSLReports.com > Site Bugs > My posts paging acting up again

My posts paging acting up again

I'm only speculating here, but...

One reason for this to happen is that a poster is on "post watch". When their contribution is approved, it is inserted into the thread in chronological order, but the updating of the "last post" indicator may actually seem to go backward. That indicator is the the "post history timme", but is updated in "wall-clock" order.

Clear as mud?

reply to Hall
Or else the post was removed, which would show the same thing.

reply to Hall
I thought along the lines of post watch too, but I have no way of knowing this kind of stuff, so...

As for a post being removed, look at the time of NeoGeo's post in my first image and the time of the anonymous poster's post in the second image. They're the same and I doubt it's a coincidence.
--
-= Mindspring MaxDSL via Covad 1536/384 TeleSurfer Pro =-

reply to Hall
Most likely, the NeoGeo64 post was not released from the watched queue until after the anon post. As 'splained by Spensergig above, the thread listing ("posts1") is updated when a post is released (usually when posted initially) but the thread itself is built dynamically each time it's displayed, but the posts are in their original time sequence.

It would be nice if the thread listing properly updated and displayed in this case (and in the case of post deletions) but that's not considered enough of a bug to warrant the effort necessary to fix it.

As for the time anomaly, that is set when the latest post is initially registered. The "last posted by" is set as outlined above.

Once you've finished banging your head on the table, here's a couple of aspirins...
--
Open your eyes see the lies right in front of you.

reply to Hall

Most likely it's the scenarios that tmpchaos or RadioDoc provided you.

1. Either the NeoGeo64 post at 10/6 7:03 was;

A) deleted.

B) deleted, then the delete tag trimmed out.

B) trimmed out.

C) The post was approved at that time, regardless of when it was posted.

The thread time, "10/6 7:03" is reflective of a change to the thread. It's just the post may fall under moderator action. I wouldn't take the thread time that seriously. If it shows an update occurred, then it probably did, but you may have not had an opportunity to view it.

And if RadioDoc's aspirin doesn't help, may I offer Tylenol?

--
...RFC143, protocol compliant.

Got it!
Thanks to your more detailed comments, I went and looked at the thread.

I think it's a mix of two oddities.
The "Last Poster" tag was applied as NeoGeo64 due to post watch - so he's the last poster even though Techie2000 last a post after him.

Then an anonymous poster came along.
Anonymous posts do update the "Last Post" time, but do not show a poster identity. The previous one is left untouched.

Voila! You now have a "post time" for one person and a "posted by" for another.



No real bug.

Dude, you ROCK!

I didn't check the time of the anon, but you're 100% right.

NeoGeo64's post was approved after Techie, so he's the last update to the name.

Then the anon posted, which is the last update to the time.

That would make multiple choice E.

And gives us a new entry entry in the Site Bugs FAQ, so we can put these threads to bed.

--
...RFC143, protocol compliant.

And upgrade to Ibuprofen...