1.5.1 Track & Pingbacks

Would you like us to start a new thread? I don’t think we’ve gone off topic.

Sorry.. no. I meant that I had started a new thread on this.

::still confused::

There have been a lot of posts about pings / tracks.
So this morning I tested this with the upgraded TestTrack blog I have for use, and another blog that I created. This other blog was hosted on another server / company.

I then tested pings and tracks.

Both worked first time, no errors, no problems.

This would suggest that those people claiming that 1.5.1 has the problem are wrong – it is almost certainly a host problem.

That is entirely possible, but I feel that the real question is, why can I send and receive *backs from every blog except your test blog? I mean, granted I can’t received pingbacks from Owen’s test system, but at least I have a server error log entry that explains why. Either way, *backs worked perfectly for me and still do under WordPress v1.5.0. The comical thing is that this switch to using CURL for the *backs rather than fopen() was to fix a server-related issue. This fix now appears to be causing more server-related issues that the initial problem.

I have no idea – that’s why I went and tested what I did.

The TT blog (my domain actually) is now hosted by A Small Orange while the blog I installed and tested against was on the original host where it never had a problem. So as to why ? Not a clue I’m afraid but the volume of posts here dictated that they did need testing so I’ve done what I can.

I just tested thru Pingomation today.

I can receive pingbacks.
I can receive trackbacks.
I cannot send pingbacks.

I was able to send trackbacks yesterday, so I didn’t do that today.

Podz, thanks for all that you’ve done. I feel that the more we test, the more confusing this gets.

Bryan, I don’t think there’s a way to test sending pingbacks with pingomation, just trackbacks. Is there?

I’ve tried sending both TB and ping from Pingomation, but only the TB worked correctly. I checked the details box and it gave me a long description of errors, mainly because of this
fclose(): supplied argument is not a valid stream resource in <b>/home/mysite/public_html/blogtest/xmlrpc.php</b> on line <b>1189
Both TB and ping work well from Podz’s TT site: see here

::hosting provider switch is being considered::

Angsuman wrote (on previous page):
“Currently I override WP 1.5 pingback with my plugin which allows me to successfully pingback to several servers.”

That plugin might help some people. Do you have it available for download somewhere?

I will make it available. I just have to write some pretty documentation to go with it. I am sucker for good documentation ??

@macmanx This is truly confusing what you are facing. I will check the 1.5.1 code to see if I notice something out of ordinary.

I bet you guys couldn’t wait for this to get more confusing? Guess what, it is! ^_^

Notice my post that I made on May 10th: https://www.macmanx.com/wordpress/archives/2005/05/10/wordpress-v151-bugs/

In that post, I linked to one of Bryan’s posts: https://blogged.btvillarin.com/2005/05/09/151/

Now, take a look at Bryan’s post. He finally received my pingback today, on May 14th.

Now that is very confusing.

Either way, I’ve moved hosts for the last time and have applied last night’s changes. I think my track and pingbacks are working as correctly as possible. Time will tell.

Please remember that moderation is on BY DEFAULT now in WordPress, so you can’t expect your pingback or trackback to show up immediately anywhere.

Yes, but 4 days? And, Bryan is just as shocked as I am.