WP-APP Update #2

I have been receiving a few bug reports for WP-APP and I have not only fixed those but have made a lot more progress implementing the rest of the protocol. Besides we shall soon see another draft (-10) of the Atom Publishing Protocol.

I have been learning more than I ever thought I would about WordPress, but since I use it on my website, I might as well know its source. I am starting to take some notes and hopefully someday share what I have learned in PHP so far, although I should be learning more powerful languages instead. Anyways, I often find myself wondering if WordPress has function to do X and if not that I will have to implement, but so far it has been great. My main lesson so far when implementing APP in WordPress is to look in xmlrpc.php first before thinking I have to write my own function to do X.

Many have pointed out how unRESTful it is to use cookies for authentication but I think RESTafarians are too religious in my opinion. They hear the word cookie and they call out heresy!. In my very own limited experience I have found out that WordPress is stateless. The cookies are simply the username and password hashed for purposes of authentication. Matt Mullenweg has impressed in me how important is to write PHP in a way that will work in a wide variety of hosting environments (but this is a painful as making HTML work across browsers). And as I pointed out to the APP WG, you don’t have access to the Authorization header in PHP when running in cgi mode. Anyways, I have listened to the RESTs and have figured out how run WordPress as a PHP module in Apache on my Dreamhost server and now it supports Basic authentication, sorry no TLS. If you care, you can point the APE at my WordPress Atom endpoint and see some useful messages on the APP dialogue between the APE and WP-APP.

Besides running PHP as a module and some tidying of the code, I have begun implementing media support. The most rewarding aspect of it so far, is that WordPress db model is incredible well designed and flexible that I have not had a need to make any changes to it yet (and I come from a very flexible data model “imaginary” world: RDF). Anyways, if you run the APE, you’ll notice some messages regarding sucessful posting of images, etc. It’s not all super complete, but neither is the APE. Anways, I must start working on some of the latest accepted paces in the APP wiki.

Last, but not least, I now support draft entries, but not with the pub:control element, instead I’m already using the app:control element. This was one of the trickies part so far in my work with WordPress, due to the security and hacking the queries (thanks God for filters in WP) to get what I wanted. And since I haven’t heard from Matt on wp-plugins.org, I have created my own SVN repository for WP-APP.

Enjoy and keep the bugs coming in and easy on my disk space please

UPDATE: In case you are wondering, I have been working too much on this that I have not had a chance to name my youngest child (Baby 3.0).

About this entry

You’re currently reading “WP-APP Update #2,” an entry on Elias Torres

Published:: 08.31.06 / 2pm

Category:: Atom

About

I’m married and father of three.

I’m a Christian and worship at CBC.

I co-founded Performable.

I’m a java, python, javascript hacker.

Here’s my FOAF file (and URI).

I’m an amateur photographer.

I work on the Web.

I participate in Open Source software development (Roller, Abdera, RDFLib, WordPress).

You may contact me (email or jabber/gtalk) at .

Dan Smith 08.31.06 / 4pm

I just switched to wp last week, i’ll give this a go

dbt 09.15.06 / 3pm

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.

Jens Alfke 09.19.06 / 8pm

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.

Elias Torres 09.20.06 / 10am

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.

J Wynia 09.23.06 / 9pm

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?

Elias Torres 09.23.06 / 9pm

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.

Implementing the Atom Publishing Protocol, 13/09/06, World according to Kieran 11.07.06 / 6pm

[...] 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

[...]

Andy 04.25.07 / 4pm

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

I am using this entry …

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

Testing the Atom API

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

Testing the Atom API

Recording Errors in PHP Apps - mick brogan 03.31.09 / 2pm

[...] * 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 [...]

Elias Torres

WP-APP Update #2

About this entry

Comments are closed

Recently

Categories

Monthly Archives

About

Pages

Elias Torres

WP-APP Update #2

About this entry

Comments are closed

Links

Blogroll

Recently

Categories

Monthly Archives

About

Pages