Q: Which version of WordPress does the App work with?
A: The App works with WordPress.com and WordPress 2.7 or higher.
Q: Which device will this work with?
A: The App works with all models of iPhone and iPod touch.
Q: My blog is located in a folder, and resolves to http://example.com/blog. How do I add the blog?
A: Type in the full URL when adding the blog, in this case, example.com/blog.
Q: I changed my theme but previewing posts shows the old theme, how do I fix that?
A: In the current release, you’ll need to remove and add the blog back to see the updated theme.
Q: I added or removed categories while in the web WordPress dashboard. When I refresh the app I don’t see those changes — how do I sync those up?
A: In the current release, to avoid collisions, you will need to remove and add the blog back to see the updated categories.
Q: How do I remove the blog?
A: Tap the blue arrow on the right of the blog listing page and then tap “Remove Blog.”
Q: Can I adjust the size of photos uploaded from the app?
A: When setting up the blog, you can choose whether to have all photos resized to 640×480 for faster uploading. This can also be changed for individual posts by selecting a post and going to the Settings screen.
Q: Adding a blog is taking a long time or times out. How do I fix that?
A: Adding a blog is dependent on the speed of your Internet connection, so if you have a very weak signal or a slow EDGE connection, try again when you are in 3G or WiFi mode.
Q: I can save posts to local drafts but can’t figure out how to publish to the blog — what do I need to do?
A: When you are ready to publish, change the status of the post (from the Write screen) to “Published” and then tap “Save.”
Q: How do I delete a local draft post?
A: In the list of local drafts, swipe your finger from left to right over the title of the draft. A “Delete” button will then appear. Tap “Delete” to remove the draft.
Q: I get an “XML-RPC Service for you blog cannot be found” error but I have XML-RPC enabled, what do I do ?
A: First ensure that you’ve typed in the URL correctly. If it’s correct, and you are on self-hosted WordPress, verify that xmlrpc.php is functioning properly. Locate your RSD meta tag by viewing-source on your blog. It will look similar to this:
<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://example.com/xmlrpc.php?rsd" />
Next, follow the link, http://example.com/xmlrpc.php?rsd, and make sure it resolved to an XML file. Locate the WordPress API item: http://example.com/xmlrpc.php. And lastly, load that apiLink value into your browser. If everything is setup correctly, you should see this message: “XML-RPC server accepts POST requests only.”
Q: I followed the XML-RPC verification steps above, but I get a different message or the RSD page loads very slowly. Now what?
A: Check with your hosting provider or system administrator to see if permissions or other issues are causing the error. If you receive a “Precondition Failed” that is most likely a mod_Security issue discussed in this WordPress Support Forum discussion. If the RSD page loads very slowly, read up on this.
Q: I checked the RSD and XML-RPC and everything is fine, but I still get an error and/or can’t add my blog. Now what?
A: Another common issue that can cause errors with the App is invalid characters. The easiest way to check is to go to the W3C Markup Validator and type in the URL of your WordPress site. If you get a response such as “… one or more bytes that I cannot interpret as UTF-8″ that is most likely what is causing the iPhone App to have trouble with your site.
Q: Can I use SSL to encrypt the App communication?
A: Yes. On WordPress.com blogs, all communication (done over XML-RPC) is by default going to use an encrypted connection via SSL. For self-hosted WordPress, if you have SSL enabled, WordPress 2.6.1 or later supports pointing the RSD information at the “https” version of xmlrpc.php which creates an encrypted communication link with the App.
Q: Local draft posts appear to be saved but are not retrievable – is there a fix ?
A: This issue has been fixed in version 2.0, now available on the App Store.
