Menu
▾
▴
#2909 Story pages comments are the same
I'm running Mac OS X version 10.3.4, using Safari version 1.2.2
(v125.8). I noticed that the first 2 pages of the following article
have the same content...
(first page)
http://ask.slashdot.org/comments.pl?
sid=113431&threshold=1&commentsort=0&tid=133&mode=nested&
pid=0
(secon page)
http://ask.slashdot.org/comments.pl?
sid=113431&threshold=1&commentsort=0&tid=133&mode=nested&
startat=100&pid=0
Even the other way that it can be bookmarked is the same. When
you click on the story title link within the story itself, you get a
shorter URL for the story for some reason, and a different URL for
the subsequent page. I don't know why you have it like this. I
suppose it has something to do with archiving articles and tracking
articles that are recently displayed. Here are the variant URLs...
(first page)
http://ask.slashdot.org/article.pl?sid=04/07/04/1846251&tid=
(second page)
http://ask.slashdot.org/comments.pl?
sid=113431&threshold=1&commentsort=0&tid=133&tid=137&tid=1
86&mode=nested&startat=100&pid=0
Logged In: YES
user_id=1076646
I also noticed that pages 3 and 4 have some content that are the same.
Page 4 starts with comments that are halfway down the middle of page
3. I haven't determined whether repetition also occurs on subsequent
pages, but if it occurs on the first four, there is a chance it could.
(page 3)
http://ask.slashdot.org/comments.pl?
sid=113431&threshold=1&commentsort=0&tid=133&tid=137&tid=186&m
ode=nested&startat=200&pid=0
(page 4)
http://ask.slashdot.org/comments.pl?
sid=113431&threshold=1&commentsort=0&tid=133&tid=137&tid=186&m
ode=nested&startat=300&pid=0
The repetition starts at the following comment...
"The Worst. (Score:5, Funny)
by jellomizer (103300) * on Monday July 05, @04:54AM (#9607289)"
http://ask.slashdot.org/comments.pl?sid=113431&cid=9607414
Logged In: YES
user_id=3889
Partial repetition is probably unavoidable due to the nature of threading.
But complete repetition shouldn't happen. I have noticed symptoms
consistent with this report, but haven't bothered to investigate, so I
suspect this is a real problem. This is notoriously hard to reproduce since
comments and their scores change continuously, so if anyone can find a
test case of a story that's archived (more than 14 days old) that would
help.
Logged In: YES
user_id=1076646
The story was posted on the 5th of July. I'll re-check the story once it's
archived, and let you know.
Logged In: YES
user_id=1076646
The article has been archived. The pages repeat just like they do when
they weren't archived. The first two pages are the same. The fourth page
begins with comments that are halfway down the third page, starting
with the same comment I mentioned before. I don't know about
subsequent pages, but it may be possible that there are other repeats.
Logged In: YES
user_id=1076646
I just got a notification that the bug was fixed, but I checked and it still
isn't fixed. My settings only allow comments of one point or higher,
maybe that has something to do with it. But the problem is still exactly
the same.
If this affects all your stories, then it affects everyone who participates
in discussions or moderation, because they have to go over more pages
to view comments.
Logged In: YES
user_id=1076646
It's happening again in a new story that was just posted. The first THREE
pages have the same comments...
http://science.slashdot.org/article.pl?sid=04/09/02/1830247&tid=126
Logged In: YES
user_id=1076646
It's happening yet again in a new posted story. This time, the first FOUR
pages have the same comments. The first four pages all start with the
FIRST POST. This bug not only interferes with reading the comments but
the moderation system as well...
http://slashdot.org/article.pl?sid=04/09/12/048255&tid=99
Logged In: YES
user_id=1076646
It is happening with the election poll. The first two comment pages both
begin with the first post...
http://slashdot.org/pollBooth.pl?qid=1202&aid=-1
Logged In: YES
user_id=704936
How about collapsing the duplicated messages in the second
page? And not including them in the count of displayed messages.
This would maintain the thread structure (and indenting),
but it would mark the comments as "read" (as read on the
previous page) by collapsing them to just a header.
By not including them in the count of displayed messages,
you would be assured of always having new messages to read
on each page.