Thread

Hello,

I have this code on EE 2.1.1.

{exp:comment:entries
    limit="10"
    dynamic="no"
    sort="desc"
    orderby="date"
    channel="channel1|channel2"
}
    <li>
        <em>{author}</em> on <a href="http://{url_title_path="><strong>{title}</strong></a>
    </li>
{/exp:comment:entries}

However, the output puts out comments in this comment_id order:

5, 6, 7, 8, 9, 14, 13, 12, 11, 10

Obviously that’s not in date descending order—it starts by ascending, then jumps, then descends. Putting it in date ascending order works—it gives a comment_id order of:

4, 5, 6, 7, 8, 9, 10, 11, 12, 13

I looked in the 2.1.2 and 2.1.3 changelogs and didn’t see anything having to do with this kind of bug. I’d prefer not to upgrade unless this is a known issue fixed in those builds. Can you let me know?

Thanks,
Matt

When you look at the actual entry dates, do they match that order? Are you using any sticky entries? An uzpgrade to 2.1.3 is still strongly recommneded, by the way.

When I write the query manually (basically, SELECT * FROM exp_comments ORDER BY comment_date DESC LIMIT 10) it orders fine. Shouldn’t this tag sort by the comment dates regardless of the entry dates they’re attached to?

Matt,

In my testing I have replicated to some extent and have reported it as a bug on your behalf here

same bug for me… with a count over 18 things go screwy and count order become unpredictable.

Bug now has a status of Fixed for Next Release so closing this one out