![]()
+

+

=

The only reasons why I want one.
![]()
+

+

=

The only reasons why I want one.
If you see a couple of posts bearing an author name other than my own, don’t worry; my blog hasn’t been hijacked.
Mr. John Bickerstaff, an iPhone developer who has joined the WordPress for iPhone development team, has graciously offered to help me trace down a configuration problem that I’m facing with the app, so he’ll be poking around here a bit for a couple of days.
It’s business as usual.

It’s a pity one of the bugs I found will be fixed only in 1.3, speaking of which will have a completely revamped posting workflow.
This space intentionally left blank.
中文字体测试。
Seems like there is no way in 1.2 to insert an image between two paragraphs. The workaround is to attach an image to the gallery of the post, post it to the server as a draft, reopen the draft on the iPhone, and insert text before the HTML code of the now-inserted image.
A little too roundabout for my liking…
If timezone is handled correctly, this post should be listed at the top of the Posts listing page in 1.2.
Back in November 2008, the WordPress for iPhone team posted a sneak preview of Version 1.2. Notable new features in this version include auto-rotation between portrait and landscape modes, comments moderation, and the ability for a user to create and edit Pages.
Some days ago, the team announced the impending start of private beta testing. To my delight, I received an email today from WordPress that I have been included in the beta test. So here I am typing out this post with v1.2. Everything’s looking good so far in the first 10 minutes of test driving…
I will be trying out every functionality of 1.2 for the next couple of days; you can expect some posts that’ll make absolutely no sense. :P
For those of you who are using WordPress for iPhone 1.1, one of the most prominent bugs introduced with WordPress’s upgrade to WordPress 2.7 is that a post published from your iPhone will become a sticky post. The WordPress for iPhone team is fully aware of this bug and will rectify it soon.

On the heels of the first-generation iPhone, WordPress released its very own blogging client application for iPhone and iPod touch. I was very intrigued by what WordPress had come up with but was never able to try it until now.

The verdict? The WordPress for iPhone app rocks!
If you are someone who blogs frequently, iPhone or iPod touch + WordPress is a fantastic combination. Having tried just about every blogging client to use on my Sony CLIÉ, and finally giving up because none of them were any good, the WordPress app is like a breath of fresh air. But having said that, there is one thing about the app I hope WordPress will improve on.

If your iPhone or iPod touch is not connected to a network, and you tap on a recent post, a dialog box pops up saying “No connection to host. Editing is not supported now.” What I’d like for the app to do is to store published posts locally, so that I can tap on a recent post and see it the way it was published, in a Viewer mode. Then, if I want to, I can choose to open this published post for editing. This is how my desktop blogging client—ecto 3 for Mac—works, and it’s be nice if the WordPress app did likewise in a true offline mode.

That aside, I think I’ll be using this app quite a lot. Writing a post on a handheld device has never felt this pleasant before…
Punk’d by WordPress :P
So… WordPress rolled out this cool new feature, ‘Comment Reply Via Email’, a week ago, right? Whenever someone posts a comment on your blog, WordPress sends you an email notification, and, instead of clicking on a reply link within the email to fire up the browser (like how it was done before), you can now hit “Reply” in your e-mail client and send off a reply email that WordPress will parse and post as a comment made by you on your blog.
All in all, pretty neat, and a great time-saver. Except when I tried out the feature for the first time just a while ago, WordPress happily went and included my email signature—containing my real name, address and cell phone number—as part of my reply, details I definitely do not want published on my blog.
That’s not so cool, since I now have to manually delete the signature that my email client automatically inserts into every new composition every time I reply to a comment. Maybe the folks at WordPress should consider configuring their servers to recognize the
--that typically precedes a signature as the end of the text in a comment reply. This way, users get the option of whether their signatures get included or not simply by tweaking their signatures accordingly.So, for all of you intending to use this feature, remember to delete in your reply email all that you don’t wish to be included as part of your comment reply. Quoted text in the reply email is automatically ignored, however, so you don’t have to fret about having to delete that whole chunk of quoted text.
Update 14.05.09
‘Comment Reply Via Email’ is supposed to automatically parse out signature blocks just like the new ‘Post by Email‘ feature. Matt Mullenweg responded to my post in the comment threads on that page, advising that there is a bug that is preventing this from working correctly.
Thank you, Matt.