Relative URI and APP Test Site
I believe I found a possible bug in the APP test site at http://bitworking.org/projects/apptestsite
I was trying to PUT on the Edit-Media URI that returned from the entry, but all I got was Not Found errors. After having a little conversation with takemaru san, it turned out that the base URI of the Edit-Media was not the URI of the entry but the collection's URI.
If you GET
http://bitworking.org/projects/apptestsite/app.cgi/service/media/416/
The server returns an entry with following Edit-Media link.
<link href="416/;media" rel="edit-media"/>
So, combining the two,
http://bitworking.org/projects/apptestsite/app.cgi/service/media/416/ + 416/;media
you get,
http://bitworking.org/projects/apptestsite/app.cgi/service/media/416/416/;media
Dah, that is Not Found on the server. The correct URI is http://bitworking.org/projects/apptestsite/app.cgi/service/media/416/;media
I just sent a mail to the developer, so I hope that will be fixed soon.
[update] Today, I confirmed this has been fixed. (2008/02/12).
But I found another bug.. //feed/entry/link@rel="edit-media" should not be in a normal entry.
AtomPub client – progress so far
Here is the early alpha of the Atom Publishing client I've been working on. The basic features work OK, but it seriously lacks usability. You probably don't wanna use it just yet even if you're a developer.
The hardest stuff would be to figure out the effective way of sync'ing. The UI is also very hard, but pretty much any UI design is difficult and time consuming. So, well, stay tuned.
WordPress 2.3.1 and AtomPub [update2]
I've noticed a couple of things while messing around with the latest WordPress's Atom Publishing Protocol support.
- Bug: Malformed XML returns when GETing a Media Link Entry.
- Bug: 404 Not Found error on GETing a category and a collection document if "WordPress address" and "Blog address" are different.
- Bug: Entry's published, Updated and Edited time stamp are always the same.
- No Etag.
- No "page", "tags", support.
Missing Etag support isn't a big deal for me because it's easier to develop a client and test with... at least for now. But, the XML error is kind a annoying.
Where am I supposed to report this, by the way? I'm kinda late for the bug hunt.
After asking in the wp-hacker list, I was instructed to join the wp-xmlrpc list.