• nils chr.

    (@nils-chr)


    Some child comments drop out of the hierachy and are displayed as if they were comments to the post itself, and not to their parent comment.

    This has occurred on posts w. 50 comments or more.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    Kermit

    (@chaosthethird)

    This probably has to do with a setting under “discussion”.

    “Enable threaded (nested) comments [5] levels deep”

    5 is the default, but it can be raised to as many as 10. I’m guessing that a thread with more than 50 comments probably has some replies that are more than 5 deep.

    Thread Starter nils chr.

    (@nils-chr)

    This probably has to do with a setting under “discussion”.

    “Enable threaded (nested) comments [5] levels deep”

    5 is the default, but it can be raised to as many as 10. I’m guessing that a thread with more than 50 comments probably has some replies that are more than 5 deep.

    I think the problem lies deeper than that. – Nested comments don’t have a ‘reply’ button under a comment that is at the deepest level and therefore the settings prevent an entry of comments deeper than what is specified ‘discussion’.

    I have tracked the problem in the jetpack/WP source & database and it appears that for some reason the level gets messed up during data retrieval; A comment that has a parent_comment_ID > 0 should not end up at level 1. But it does, sometimes.

    The code in that area is very messy and hard to debug. In my opinion the the new comment system by Jetpack is too fancy for its own good.

    The way Jetpack hooks into the code is also very ‘selfish’ (quoted from the developer’s comments in the code). It blatantly removed the pre-comment-form filter I had made. That’s not accoording to the WP standards that presses the importance of not breaking other developers’ plugins.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Jetpack comments – child comments drop out’ is closed to new replies.