Thanks to the hard work of Elias Torres and Pete Lacey WordPress 2.3 beta 1 has significantly upgraded support for the Atom Publishing Protocol.
The apptestclient and APE may also be used to verify your installation.
Thanks to the hard work of Elias Torres and Pete Lacey WordPress 2.3 beta 1 has significantly upgraded support for the Atom Publishing Protocol.
The only post installation instructions required are to create and set permissions on the uploads
directory.
cd wordpress mkdir wp-content/uploads chmod 777 wp-content/uploads
The apptestclient can be used to verify your installation.
svn checkout http://feedvalidator.googlecode.com/svn/trunk/apptestsuite cd apptestsuite/client python appclienttest.py --name=admin --password=password http://example.com/blog/wp-app.php/service
The APE may also be used to verify your installation. If your WordPress blog is public, you can use the APE directly from the web. Otherwise the APE can be installed locally on a Ubuntu Feisty Fawn (instructions for other operating systems may vary) and run thus:
Obtain a Java.net account
cvs -d :pserver:rubys@cvs.dev.java.net:/cvs login cvs -d :pserver:rubys@cvs.dev.java.net:/cvs checkout ape
Place the following into src/go.cgi
:
#!/bin/bash ruby go.rb
chmod +x src/go.cgi
sudo gem install builder sudo mkdir /var/www/ape sudo chown `id -u`:`id -g` /var/www/ape cd /var/www/ape wget http://www.tbray.org/ape/ wget http://www.tbray.org/ape/ape.css wget http://www.tbray.org/ape/ape_logo.png wget http://www.tbray.org/ape/info.png sed -i 's/go" /go.cgi" /' index.html
Now, adjust the paths and drop the following into /etc/apache2/conf.d/atompub
:
Alias /atompub/ /home/rubys/cvs/ape/src/ <Directory /home/rubys/cvs/ape/src> Options +ExecCGI AddHandler cgi-script cgi </Directory>
sudo apache2ctl restart
In addition to being able to be run at http://localhost/ape
, it can be run directly from the command line:
ruby go.rb "uri=http://example.com/blog/wp-app.php/service&username=admin&password=password" > report.html sed -i '1,/^\r$/d' report.html
The apptestsuite and APE outputs will be updated hourly with the latest code from CVS and SVN until Wordpress 2.3 is released, and XMPP IMs will be sent to me upon failure.
In the first example, shouldn’t that be wp-content, not wp-contents ?
And in a production (i.e, hosted) environment, it’ll be “chmod 777 wp-content/uploads”, because only mummy can chown.
I’m very much looking forward to this release too and have to thank Elias Torres, Pete Lacey and Sam for making this possible! I expect that with this, all bugs in WordPress 2.2.x leading to validation errors in the Atom feeds will vanish with 2.3. That, on top of full AtomPub compatibility, is truly amazing.
I’m awaiting the day I can press the “reply” button in my feed reader to make a comment on a blog entry with great joy and excitement! :-)
all bugs in WordPress 2.2.x leading to validation errors in the Atom feeds will vanish with 2.3
That’s a tall order. But are you aware of any such bugs? If so, I will definitely look into it.
So Wordpress 2.3 will chmod the uploads directory to 777?
That’s not my experience. If the directory does not exist, Wordpress will attempt to create it. But in my case, not only was the directory was not there, the parent directory wasn’t writable by the Apache process. The inevitable result was that tests involving uploads failed.
Ticket #4887 (closed defect: fixed)
Elapsed time from submition of patch to being committed to the trunk: 93 minutes.
Four sanitization warnings will appear or disappear based on whether or not the role assigned to the username Ape uses has unfiltered-html capability: