pingbacks broke …

OK MORE: Latest Jetpack has broken pingbacks. Have tested by deactivating/posting/reactivating. Behavior consistent and broken as described.

Same thing happened two versions ago, the JP team released a fix almost immediately. Not so far on latest version.

Any plans to address?

I’m sorry to hear you’ve run into issues.

However, I’m not sure what you’re referring to. I also don’t recall that bug we fixed 2 versions ago. Could you tell me more about your issue? What happens when you ping another post, on your site or on another?

Thanks!

Hi Jeremy.

It’s POSSIBLE I’m confusing the “earlier version” issue with the same problem cropping up in two quickly-released versions of Akismet, but in the present tense, here’s what I know.

Since the latest Jetpack update, Pingbacks I write are not going through. This statement applies to both internal pingbacks and external ones.

If I deactivate Jetpack and edit a page that has outbound URLs, the pingbacks flow. If I deactivate Jetpack before hitting publish the pingbacks flow (and then I reactivate Jetpack). But with Jetpack enabled … nothing.

I understand the ever-popular “maybe it’s an incompatibility with some other plug-in” conversation, and I accept that’s possible, but since the issue started right after the update and since I can address it as I do … I kinda thing it’s a Jetpack “thing”, you know?

BTW: I have only the following Jetpack modules active:

Enhanced Distribution
Extra Sidebar Widgets
Related Posts
Sharing
Subscriptions
Stats

ALSO: I’ve got the related posts widget configured to show six posts instead of the default 3, using this code in my child theme’s functions.php:

<strong>}

function jetpackme_more_related_posts( $options ) {
    $options['size'] = 6;
    return $options;
}
add_filter( 'jetpack_relatedposts_filter_options', 'jetpackme_more_related_posts' );</strong>

Thanks for looking!

That’s interesting. I can’t think of any code in Jetpack that would affect the behaviour of pingbacks. I also tested pingbacks between 2 sites of mine, both running Akismet and Jetpack 3.4.1, and pingbacks seem to work:
https://i.wpne.ws/aQpL

Do you happen to use security plugins on your site, or anything that would disable XML-RPC pingback requests?

Could you also go to Settings > Discussion in your dashboard, and make sure trackbacks are enabled there?

Hmmm.

I use Wordfence for security, and also run a couple of user filtering plugins, but there genuinely doesn’t seem to be anything in any of them that should be blocking xml/rpc.

(and yes, of course trackbacks are “enabled” … I did check for you, though) ??

Your security question is well taken, though: now once again … all worked until this version of Jetpack, so … I don’t think that’s it UNLESS there’s something in Wordfence that is naturally at odds with the latest JP update. Any broad thoughts on that or the need for “extra” security, to begin with?

BTW: the caching add-on in Wordfence is spectacular, AND compatible with everything else I have running, so if possible I’d like to keep using it!

And again, I can replicate/fix/break by disabling/re-enabling Jetpack …every time. I’m just … stuck!

I don’t believe Wordfence includes any setting to allow you to disable XML-RPC pingback requests. It’s also compatible with Jetpack, so you can use both plugins without any issues.

Could you post your site URL here, so I can run some tests?

If you want it to remain private, you can also contact us via this contact form:
https://jetpack.me/contact-support/

Jeremy, I’m happy to post here; I just hope the forum moderators allow it (there’s been some controversy)

[Moderated – Please conform to the WordPress trademark]

Thanks…

Since your site URL seems to violate the WordPress trademark, could you use the contact form I mentioned above instead, and mention this thread so I can follow up with you?

Thanks!

Jeremy, I appreciate your wording and thank you for leaving “seems to” in the conversation. ALLOW ME TO POINT OUT that wordpress.domainname.com is NOT a violation.

I’ll take this offline, as you requested …

*Raises hand and does the time out thing*

Hi Jeff, I’ll try and explain it simply.

If you post this URL https://wordpress.answerguy.com/blog/ then yes, that’s fine and there will be no problem as long as it doesn’t redirect to the other URL. The other URL which uses a domain name that contradicts the trademark statement at this link.

https://wordpressfoundation.org/trademark-policy/

I’m sure you know which one I mean. ??

The moderators moderate these forums. While you disagree with what the trademark owners have clearly and succinctly stated in that URL, there’s also this link and verbiage.

https://www.ads-software.com/about/domains/

This isn’t new to you and I don’t want to (and won’t) get into it with you. But please be aware that while we’re not the trademark police, that URL will get pulled when found.

Back to your regular scheduled topic: I suggest, as you’ve stated, that you avail yourself of Jeremy’s offer. That may lead to solving your problem.

Jan, I kid you not when I say I appreciate you chiming in. Yes, we understand each other.

And I’m sure you realize the redirect is not a trick of any sort; it’s just how things “are” are the moment. AND: (I’m serious) often the redirect never happens; we see people go the the wordpress-dot link and stick there … except when they don’t.

Thanks; this was re-sent through the support form; Hopefully it finds its way to Jeremy ?

this was re-sent through the support form; Hopefully it finds its way to Jeremy ?

It did! ?? I just replied to your email.

I’ll mark this thread as resolved, and we can continue our conversation via email.