[wp-trac] [WordPress Trac] #34110: WordPress Trackback Bug when Comment Pagination is Enabled

WordPress Trac noreply at wordpress.org
Thu Oct 1 11:40:37 UTC 2015


#34110: WordPress Trackback Bug when Comment Pagination is Enabled
--------------------------+-----------------------------
 Reporter:  isaumya       |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Comments      |    Version:  4.3.1
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Hi, I just find a comment bug with wordpress which I think is there for a
 ling site, may be since v2.7+ but never actually fixed.

 '''Bug Details/ Reproduce process'''

 Inside your theme while fetching your comments after
 {{{
 have_comments()
 }}}
  try to fetch comments only by using
 {{{
 wp_list_comments( array( "type" => "comment") )
 }}}
  and then below check if trackback exists and if they do print the
 trackbacks separately using
 {{{
 wp_list_comments( array( "type" => "pings") )
 }}}

 Now add a bunch of comments on any of your blog post which also have some
 trackbacks. Add more than 60 - 70 comments on that post. and from settings
 enable comment pagination option. So that comments get divided into
 several comment pages. If you are thinking this is never going to happen
 in real life, let me tell you I have blog posts which has more than 2.500
 comments in it and none of them are spam comments.

 Now, after you enable the comment pagination, visit your blog page link
 i.e. example.com/some-post/ and you will see the trackbacks below your
 comments as it should show up now start navigation through your comment
 pagination, you will see the following -

 Trackback is showing on the normal blog post link
 Trackbacks also showing for /comment-page-1/

 But when you will move further from comment page 1 you will only see the
 heading i.e. Trackback or whatever you have set, but not the actual
 trackbacks. This problem is also present in genesis theme, earlier I
 though it was a genesis bug but while developing a non genesis wordpress
 there I understood that it is actually a wordpress core bug.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/34110>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list