Comments on: WordPress 3.1 and XML-RPC

By: Sdílení jedné databáze « Fórum podpory WordPressu

Sdílení jedné databáze « Fórum podpory WordPressu — Wed, 27 Jun 2012 10:08:34 +0000

[...] se pustíte do propojení samostatných webů, tak doplňuji několik zajímavých odkazů (1, 2, 3), kde naleznete inspiraci… Příspěvek je starý 8 měsíců [...]

By: hakre

hakre — Sat, 25 Dec 2010 12:33:44 +0000

No, it’s not different to use to previous versions. The changes are related to the method how HTTP requests are done (now more flexible) and (which was not demonstrated by Otto in his post) that it is now more easy to extend the class. See http://core.trac.wordpress.org/ticket/10588 and http://core.trac.wordpress.org/changeset/16064 . The changes are AFAIK backwards compatible. They might not be if you included the library on your own for special purposes.

By: Derrick Tennant

Derrick Tennant — Fri, 24 Dec 2010 06:20:29 +0000

It’s late and I’m tired from putting Christmas together, so forgive me if this is a stupid question.

Is this different than the XML-RPC in previous versions? I wrote some code a few months ago for a client that scraped their old non-wp-compatible site, converted the data as necessary, and posted their content, including featured images.

I’m probably missing the point of this all together

By: Furcifer

Furcifer — Thu, 23 Dec 2010 23:39:29 +0000

Otto Im curious, would this enable something like i.e. a single signup across multiple blogs across multiple servers across the web, would be a neat way to bring the blogging communities together without having to rely on third parties, i.e. facebook or twitter connect as a great deal of sites don’t enable either for one reason or another.

Am I making sense?

Jay

By: Otto

Otto — Thu, 23 Dec 2010 21:14:29 +0000

Yes, well, my sample of hosts is probably not representative of the whole.

The few I’ve had problems with fsockopen in the past have usually had curl installed, so the http api stuff worked fine for those cases, and I just used that instead.

By: Joseph Scott

Joseph Scott — Thu, 23 Dec 2010 21:12:45 +0000

Interesting, the Akismet plugin has been using fsockopen for years with a high degree of success. The biggest problem it had was lack of proxy support, which we got for free after moving to the WP HTTP API.

By: Otto

Otto — Thu, 23 Dec 2010 21:08:13 +0000

Sometimes it worked, sometimes it didn’t. Depended on the host. Lots of hosts block fsockopen.

By: Joseph Scott

Joseph Scott — Thu, 23 Dec 2010 21:06:12 +0000

The original IXR code uses fsockopen, that doesn’t work for you? That said, converting to the WP HTTP API is worth while. Picking up the proxy support alone would be reason enough.