Hi everyone, and thanks for taking the time to give us your feedback. It's really helping us to nail down issues with Direct Publishing before switching the whole site over to the new version of SocialSpark.

For most configurations, AtomPub just works after it's enabled in the WordPress admin interface, but in the case of PHP run as CGI on top of the Apache web server (forgive me for getting technical here), additional Apache configuration may be required. This is a well-known issue with Dreamhost, and likely many other hosts as well.

PHP run as CGI is the most common of the few issues we're seeing with WordPress. Another possibility, as Jonamerica mentioned, is a WordPress installation that is in a non-standard location (i.e. your blog URL is someurl.com but your WordPress is installed at someurl.com/blog).

Another possibility is an issue with your server's configuration. There's a pretty technical explanation of possible server issues on WordPress's site. And a final, less common issue is a version of WordPress that is very old and does not support AtomPub (if that is the case, we strongly recommend upgrading, at the very least for security reasons).

We are working on a solution for the first few issues now. One will give users a fall-back in case their server configuration is rejecting AtomPub credentials passed over Basic Auth (again, forgive the technical language). Another fix will allow users to tell us if WordPress is installed in a different location from their blog. Please hang tight while we work to implement these workarounds for you, and thanks again for providing this valuable feedback.

Regards,

Jamie Kite
Product Owner, SocialSpark.com