Update on WordPress for iOS

Version 2.6.2 of the WordPress app for iOS devices was not quite the salvation we hoped it would be. While it solves some of the issues presented in earlier versions of the app, many of you are still experiencing problems that make the app difficult to use. Therefore, starting today, the entire team is going to focus on fixing these issues and hopefully ship improvements to you a lot faster.

Thanks to the crash reporting system built into 2.6.2 we now have a deeper understanding around some of the crashes, and therefore we’ve been working on a Crash Fix release which we’re hoping to submit to the app store shortly.

The single most valuable thing that has helped us understand the problems in the app, however, is the feedback from all of you guys. Keep it coming!

If you’re still experiencing problems, please let us know about it in the WordPress for iOS Forums. We’re trying to keep up with all your posts.

Comments

If you need support for one of the WordPress apps, visit our support page.

  1. Cool. I’ve been disappointed with the last few updates, but I have faith in your team. WordPress shall have a mobile client all others aspire to be!

  2. Ironically 99% of my issues went away once I switched hosts (went from a general shared hosting environment to a WP only specialized one—boy what a difference that made!).

    I’ve run across a few bugs, but that might be because of the new iOS 4.2 update. 😦 (it’s making Pandora screwy for me, along with a few other apps).

    Anyways, thanks for the effort! :-)

  3. Hey Darnell, do you know what made things not work out on your previous host? Many users are having problems because of limitations on their host for their self hosted WordPress blog, and we’d really appreciate it if you’d share your experiences here. :)

  4. Hi Darnell!
    Mind sharing who you switched to for hosting? I run into a lot of limitations with my host, especially picture upload sizes, which is hugely annoying! 😦
    Thanks for your help!
    Kaisha

  5. Definitely having weird issues on my end even tho I turned on the xmlrpc support and fed the app the path. Doesn’t log me in consistently. Nice idea tho, waiting patiently for wonderful developers to fix it and make it end user friendly. :-)

  6. Sure thing! From what I could gather many shared hosts limit the number of CPU resources each blog has, and depending upon your “plan” will bump you up.

    If blogs start using too many CPU resources, they put you in “throttling jail” where they drastically reduce the number of resources you can use to very pathetic levels.

    Even after making changes to the .htcaccess, etc., my host still limited my blog to how many resources they allocated, which made video uploading impossible as I would (once again) go over their imposed limits resulting in more jail time.

    Most hosts that promise unlimited hosting and bandwidth do this to users, which sucks as they’re not interested in making their servers work with WP, but instead focus on stuffing as many blogs upon a server as possible.

    I think Automattic needs to provide a list of what server settings work best for WP, and encourage their users to ask their hosts to make the necessary changes.

    I guess I wrote a small novel here, but that is the gist of my experience. My old host account should be expiring in the next 6 days, so if you want I can do some more testing. :-)

  7. This app seems to have serious issues.

    On a WordPress.com site I have 3 posts. Select one to edit and start typing. Then click to copy text etc from another post and going back to the one I’m editing. All edits I made are gone! Then I see the save button. You don’t even want. Save button. Autosave. We need a publish button, perhaps. But really a save button makes no sense.

    Tom Andersen

  8. Hey Tom, I hear your frustration. We do want to implement autosaving in the future but have to prioritize a bit when it comes to new features – currently we’re working on nailing remaining crashes that we get reports about and a lot of minor bug fixes.

  9. The publishing date and time that I can configure my post to be is not working properly… Apparently, it’s not following to my time zone I presume.. It’s +8 here..

  10. My problem is as follows (NB: self-hosted blog)…

    – type in URL of site, the admin username and password; nothing (get msg “Incorrect username or password”).

    – add “/wp-admin” to the end of the URL and suddenly authentication apparently happens. Leastwise, I get another field “XMLRPC” us that I’m supposed to fill in, I guess. That’s in the base directory, so I type in the same URL (drypond.com). Bang! “Incorrect username or password” message comes up.

    It seems to me that there is a mismatch between the address where login occurs (/wp-admin) and the location of the xmlrpc.php file (in the base folder). Seems to me the app should take the location of the login details and KNOW that it exists in the /wp-admin folder. Then the location of the XMLRPC file would still be current.

    Not happy that I can’t log in to my self-hosted blog. 😦 Not happy at all.

  11. Hey there Leitchy, we have a new version of the app – 2.6.3 – that takes care of a lot of the issues people were having. If you have a moment, could you try it out and let us know how it works for you? If you’re using Twitter hit us up at @WordPressiOS or me directly at @chrisboyddotnet.

  12. Hey there Alwyn, we have a new version of the app – 2.6.3 – that should take care of this specific issue. If you have a moment, could you try it out and let us know how it works for you? If you’re using Twitter hit us up at @WordPressiOS or me directly at @chrisboyddotnet.

Comments are closed.