[wp-trac] Re: [WordPress Trac] #3052: pingback_ping() function displays wrong content in pingback-display in some occurances

WordPress Trac wp-trac at lists.automattic.com
Tue Aug 22 09:20:27 GMT 2006


#3052: pingback_ping() function displays wrong content in pingback-display in some
occurances
-----------------------------------------------------------+----------------
 Reporter:  webrocker                                      |        Owner:  anonymous
     Type:  defect                                         |       Status:  new      
 Priority:  normal                                         |    Milestone:           
Component:  XML-RPC                                        |      Version:  2.0.4    
 Severity:  normal                                         |   Resolution:           
 Keywords:  reporter-feedback|pingback|xmlrpc.php|has fix  |  
-----------------------------------------------------------+----------------
Comment (by webrocker):

 ok, actually I have to deal with 2 different "bugs".
 the first is kind-of template related:[[br]]
 1) with the original {{{xmlrpc.php}}}, page-navigation- and meta-link-
 contents will show up as excerpt in the pingback, if they are wrapped
 inside {{{<div></div>}}} tags and not {{{<p></p>}}} tags. This can be
 fixed by adding ''div'' to the regex in line 1192 of the pingback_ping()
 function as stated above.[[br]][[br]]
 the second is caused by the use of the ultimate tag warrior plugin:[[br]]
 2) if it is used to display "related posts", and the pinging post has the
 same tags as the pinged post, the link to the pinged post will appear
 inside this "related posts" navigation - and the first appearance of that
 link will trigger the "excerpt" of the pingback. since the "related posts"
 navigation can appear anywhere inside the page, depending on the template,
 there is no way to tell which instance of the link is the "correct" one to
 use for the pingback excerpt. :-(
 [[br]]
 2) will only happen with pingbacks inside the same blog, 1) happens to
 "foreign" pingbacks as well, so I think 1) should be treated as a bug and
 2)... hm, well, dunno.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/3052>
WordPress Trac <http://wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list