WordPress Trac: Ticket #37160: Pingbacks fail on multi-page posts http://core.trac.wordpress.org/ticket/37160 <p> Repro: </p> <ol><li>Publish a post to pingback in a subsequent post and assure that the site/post will allow pings. </li><li>Create a second post that has multiple pages with a reference to the post created in step 1 in one of the later pages (sample content below). </li><li>Publish the second post. </li></ol><p> Expected: The pingback will register. </p> <p> Actual: The pingback doesn't register. If you repeat steps 2 and 3 but move the link to the post created in 1 to the first page, the pingback works. Here's some sample content to demonstrate the issue: </p> <pre class="wiki">Page One &lt;!--nextpage--&gt; Page Two &lt;!--nextpage--&gt; Page Three with pingback: http://pleasetest.me/2016/06/23/page-to-ping/ </pre><p> This fails because the pingback code checks the pinging post to confirm that the pung link exists in the content. Since the pung link displays on a subsequent page, it's not displayed on the un-paginated permalink. Thus when the pingback code fetches the pinging link, it doesn't find a link to itself in the content and it discards the pingback. But this is a valid use case and not an instance of spoofing (which I take it is what this check is designed to prevent). </p> <p> I'm not sure if there's some parameter we could append to the url when we fetch to validate the link in context that might skip the pagination. If so, that might be the simplest fix. I suppose another fix might be to look for <code>verifying pingback</code> in the user agent (which is included in this validation request's UA) and skip pagination if found. That feels kind of brittle, though. </p> en-us WordPress Trac http://core.trac.wordpress.org/chrome/site/your_project_logo.png http://core.trac.wordpress.org/ticket/37160 Trac 1.2.2 ocean90 Mon, 04 Jul 2016 10:02:32 GMT version deleted http://core.trac.wordpress.org/ticket/37160#comment:1 http://core.trac.wordpress.org/ticket/37160#comment:1 <ul> <li><strong>version</strong> <em>trunk</em> deleted </li> </ul> Ticket