Anyone have an idea why this would happen, or better yet, what setting did I miss to cause this? I have over 500 comments on a time-critical post, and yet none of the ones after 500 are displaying.
And BTW, is that new? Because I did not know this before, and as recently as two months ago, I easily went past 500 comments on a post, and did not have the limit=999 in my tags then.
No, that’s not new. It’s been in forever. I’m not sure if it’s documented anywhere, I learned about it a long time ago when Patch asked why his monthly archives were cutting off early. =)
I would seriously encourage you to make use of comment pagination. Displaying that many comments on a single page just seems crazy to me; I can’t imagine what the load time would be. Paginations ought to make things a lot more manageable.
“re-numbered”? I’m not sure what you’re referring to.
If you’re using an ordered list (<ol>) to display the comments then you’re right that the list would default to starting with 1 on each page unless you specify otherwise.
Sorry I was unclear Chris, but you surmised correctly. Now that my fundraiser is over, I have in fact implemented comment pagination, and it seems to work well, but each page starts the numbering over. My guess is that there would not be much demand for comment numbering functionality that would transcend this limitation of the ordered list, but maybe I will throw in an FR anyway. I appreciated everyone’s very quick response. Thanks much.
You can specify the start value of the list if you want:
<ol start="50">
To get the value dynamically, you’d probably need to look in the URL for the pagination segment (”/P50/”). Let’s say you have this URL: http://www.example.com/index.php/weblog/comments/my_entry_title/P50/
In this case, the pagination information is in segment 4. So, you need some PHP to grab the value:
<?php
$page = "{segment_4}";
// set the offset to the pagination value, otherwise set to one
$offset = substr($page, 0, 1) == "P" ? substr($page, 1) : 1;
?>
<ol start="<?php echo $offset; ?>">
You’ll obviously need PHP parsing turned on in the Template.
Hey thanks. If I can get that nailed down, it will make this sort of thing work better in the future.
I agree with LJ’s assessment that slow page loads can deter readers, though in this case, my readers had strong motivations to stick with it, and they did. Still, I don’t want to take it for granted, and anything I can do to get my desired functionality and a better viewer experience is worth exploring.
