Comments on: WP-APP Update #2

By: Recording Errors in PHP Apps - mick brogan

Recording Errors in PHP Apps - mick brogan — Tue, 31 Mar 2009 18:07:07 +0000

[...] * wp-app.php – Atom Publishing Protocol support for WordPress * Original code by: Elias Torres, http://torrez.us/archives/2006/08/31/491/ * Modified by: Dougal Campbell, http://dougal.gunters.org/ * * Version: 1.0.5-dc [...]

By: Andy

Andy — Wed, 25 Apr 2007 20:06:24 +0000

MoJo Test
2006-04-25T06:07:20Z
Example

Testing the Atom API

By: Andy

Andy — Wed, 25 Apr 2007 20:05:11 +0000

I am using this entry …

MoJo Test
2006-04-25T06:07:20Z
Reuters MoJo

Testing the Atom API

By: Andy

Andy — Wed, 25 Apr 2007 20:04:44 +0000

I always get “HTTP/1.1 415 Unsupported Media Type” also, any ideas why?

By: Implementing the Atom Publishing Protocol, 13/09/06, World according to Kieran

Implementing the Atom Publishing Protocol, 13/09/06, World according to Kieran — Tue, 07 Nov 2006 22:03:23 +0000

[...] In the end, with the help of the Atomic Client, Tim Bray’s Atom Protocol Exerciser and Elias Torres’s public server implementation I was able to get it all working…and here’s how I did it [...]

By: Elias Torres

Elias Torres — Sun, 24 Sep 2006 01:39:09 +0000

The SVN version is a big rework of the code which is in progress. That’s why you are seeing a different behavior.

The 404 is probably because I changed the URL structure, so first get the app.php for the service document. That’ll tell you where are the collection URLs. Then get those to get entry URLs.

I’ve been busy these couple of weeks but soon I’ll be deploying the SVN version.

Thanks for using it. Please stay tuned for new releases.

By: J Wynia

J Wynia — Sun, 24 Sep 2006 01:15:19 +0000

I’m trying to figure out what’s going on on my server when I try to install and test it.

If I grab the latest version out of SVN (or any version actually, I just figured the SVN might fix it), I get an error at line 298 for only variables being able to be passed by reference.

If I move the expression to a variable and pass the variable in, it doesn’t throw a compiler error:

$scriptname = explode(‘/’,$_SERVER['SCRIPT_NAME']);
$this->script_name = array_pop($scriptname);

However, it doesn’t work and doesn’t validate though your demo version does. When I was using the original version, it was throwing a 405 error and now it’s throwing a 404.

Any ideas what I need to change to get it working?

By: Elias Torres

Elias Torres — Wed, 20 Sep 2006 14:13:12 +0000

Jens, Excellent. I welcome the patches the only thing is that I started refactoring the code and not sure if they'll be compatible. The source can be checked out using svn from my svn wp-app repository. I've been heads down with other code lately, but I plan to finish this and to test it using Joe Gregorio's APP test suite in Python.

By: Jens Alfke

Jens Alfke — Wed, 20 Sep 2006 00:17:00 +0000

It’s really coming along, but I’m still running into problems…

* It gets confused by incoming Content-Types that have MIME parameters. For example, if a POST has “Content-Type: text/xml; charset=UTF-8″, it will fail with an Unsupported Media Type error. I fixed get_accepted_content_type to strip parameters.

* Outgoing content elements are declared as type=”xhtml”, but the actual type emitted is escaped HTML. This causes the client to overly-escape the content. Both content and summary should be declared as type=”html”, with a CDATA section wrapping the text. (I had to fix this in both get_feed and get_entry, since each of these has code to generate entries. Could the core entry-generator be broken out into a shared subroutine?)

* Incoming type=”html” content gets messed up. Looks like it’s over-quoted, since the markup shows up as literals in the resulting entry. I tried to track this down, but the entry parser code is too complicated…

I have patches for all of these but the last.

By: dbt

dbt — Fri, 15 Sep 2006 19:37:16 +0000

Between this and Ben Smedberg’s Atom 1.0 Feed plugin WordPress is almost becoming usable.

Thanks, I’m using this now, it’s totally awesome.