Fixed — Well, Almost

For the past six months I’ve been trying to get WordPress to fix a bug that was introduced in November when WordPress launched version 16.0 of its iOS app for the iPhone. If I visited another blogger’s post, either from my reader or from a pingback to one of my prompts in my notifications, I was unable to like or comment on the post in question unless it had “.wordpress.com” in its URL (blog address). I couldn’t even like or comment on my own posts because my blog’s address is fivedotoh.com and not fivedotoh.wordpress.com.

Well, it appears that the fix is in. Well, kind of, anyway. As of today, when I attempt to like a post, this shows up on my iPhone’s screen:

I’m asked to log in to my WordPress account, which is weird because I’m already logged in to WordPress on the iOS app. But when tap on “Continue,” I am returned to the post in question and — hallelujah — I can like the post. Yay!

And sometimes I can leave a comment on the post, too. But for some reason, on some (but not all) posts, I will see this:

Again, I’m already logged in to WordPress, and I already came from the log in screen just to like the post, but when I tap on “You must be logged in to post a comment,” that same log in screen as shown previously appears, but when I tap on “Continue” and it takes me back to the post, the same “You must be logged in to post a comment” is still there and I can’t post a comment.

I am happy that the WordPress happiness engineers addressed the inability for me to like posts in the iOS app, although it has that extra step to do so. And while I can now also comment on some posts, I can’t on all posts.

So thank you, WordPress, for fixing the problem I’ve been bellyaching with you about for the past six months. Well, thank you your almost fixing it. There are still a few issue to be resolved.

An Old Dog Apparently Can Learn New Tricks

I have been resistant to using the block editor on my iPhone because I thought it would be close to impossible to use on the relatively small screen of an iPhone. But then the powers that be over at WordPress decided to remove the option to use the classic editor on the latest update to its iOS app. This is forcing me to either embrace the block editor on my iPhone, to quit using my iPhone for my blog and to start using a Windows laptop, or to quit blogging altogether.

While pondering my options, last night my wife and I picked up some Chinese take-out for dinner, and when I opened up my fortune cookie at the end of the meal, this is what I found inside of it:

So, I decided to heed the message in my fortune cookie and not be afraid to try something new. To that end, I’m using the block editor on my iPhone to create this post. In fact, this is my fourth post that I’ve created on my iPhone using the dreaded block editor since yesterday.

And do you know what I have discovered? I have discovered that it ain’t that terrible. It will take some getting used to, and it will take me a bit longer, at least for now until I do get used to it, to write my posts.

So I guess an old dog like me really can learn some new tricks after all.

Now if only WordPress would get around to fixing that damn bug that was introduced in its iOS app last November that prevents me from liking and commenting on some other bloggers’ posts, I’d be a happy camper.

TMP — Another Letdown

Every Monday, Paula Light, with her The Monday Peeve prompt, gives us an opportunity to vent or rant about something that pisses us off. Are you ready for another rant about WordPress?

On Sunday I was really excited that the WordPress iOS app version 17.0 was available for uploading. I figured that by now, five and a half months after releasing version 16.0 last November, and with 11 interim releases up to 16.11, version 17.0, a major release, would surely have fixed the annoying bug that surfaced in version 16.0. I installed the new version, tried it, and the problem was not fixed. So I reached out to the “hapless” engineers. I wrote…

This morning I was very psyched to upload WP-iOS version 17.0, thinking that, after more than five months since the release of version 16.0, a new major release will have finally fixed the problem. But yet again, disappointment, frustration, and anger. I’ve had countless exchanges with various happiness engineers over the past five-plus months, explaining the bug, providing screenshots, and even a video clip illustrating the issue. Over the months I have been told that the developers had been able to replicate the issue and were working on a fix. Meanwhile. You keep on releasing enhancements to that stupid block editor that few people like, you add the head-scratching ability to mark a post as “seen,” a functionality whose value I can’t understand, and add a SnapChat or Instagram-like “stories” feature that most bloggers don’t want or need. But you have still failed to fix a critical bug in your iOS app. WTF, WordPress?

I got a response yesterday saying…

I’m sorry to know it’s not working for you even after updating to the latest version of the WordPress app. We’re not able to reproduce this with our own test sites/accounts. Can we have your permission to log in to your WordPress.com account on the app to perform testing for troubleshooting purposes?

What? After all this time, they’ve done nothing? We’re back to square one. I gave them permission to log in to my account and this morning I saw this…

Thank you for giving us the permission to access your account. I was able to reproduce this on your account and my test account. I have reported this to our developers for a fix.

So, how likely is it that you think this will be my last post complaing about this as yet unresolved bug in the WordPress iOS app?

Blogging Insights — WordPress in the Time of the Pandemic

Blogging insightsFor this week’s edition of Blogging Insights, Dr. Tanya wants to know…

How satisfied (or not) are you with WordPress during the pandemic?

Up until August 2020, when WordPress decided to decommission the classic editor and force the block editor down our throats, I was very satisfied with WordPress. But I’m not a fan of the block editor and so my level of satisfaction diminished considerably.

The good news, though, is that, while the block editor is not a viable option for me to use on my iPhone if blogging on wordpress.com using a browser, I can still use the WordPress iOS version of the classic editor on my iPhone. However, WordPress has recently announced that the classic editor option will soon be removed from its iOS app, as well. And that, as far as I’m concerned, will suck.

The other consideration that has lessened my satisfaction with WordPress is that when WordPress rolled out version 16.0 of its iOS app this past November, there was a major bug in it, which I wrote about in this post on November 3rd.

Since that time, I’ve had countless exchanges with various happiness engineers, explaining the bug, providing screenshots, and even a video clip illustrating the issue. Over the months I have been told that the developers had been able to replicate the issue and were working on a fix. And yet here we are, five and a half months later and that bug has yet to be fixed.

So, overall, I have not been very satisfied with WordPress. I’m disappointed, frustrated, and pissed off.

But none of that has anything to do with the pandemic. It’s more about how the powers that be at WordPress don’t seem to give a shit about how we feel about the removal of the classic editor and their insistence that we embrace the block editor. Basically, they’re telling us that it’s their way or the highway.

And it’s also about how the happiness engineers and developers at WordPress are terrible when it comes to fixing bugs.

Unfortunately, as far as other blog hosting sites, none of them have the blogging community that WordPress does. It was that blogging community that landed me at WordPress to start with and it’s that blogging community (i.e., all of you) that is keeping me on WordPress.

TMP — Being Seen

Every Monday, Paula Light, with her The Monday Peeve prompt, gives us an opportunity to vent or rant about something that pisses us off.

It should come as no surprise to anyone who has perused my blog over the past four months that my rant today is about WordPress. On November 3rd last year, I wrote a post, “Another WordPress Bug,” in which I pissed and moaned about how WordPress had released an update to its iOS app for the iPhone. That release, version 16.0, had a bug in it.

When I went to my reader and then click to visit posts, I could no longer “like” certain posts. And if I tried to comment on those posts, it didn’t recognize that I was logged onto the app and it asked me to enter my name, email address, and blog URL. And sometimes, even when I did that, I still was unable to leave a comment. I’d never had to do any of that before from within the WordPress app on my iPhone.

Of course I’ve exchanged dozens of emails with the WordPress Happiness Engineers, who have assured me that they’re working on a fix. Almost four months have elapsed since that release and every time WordPress issues a new release, I get my hopes up that the bug will have been fixed.WordPress just released version 16.7 and, once again, my hopes have been dashed. The annoying, frustrating bug persists. But one of the “enhancements” introduced in version 16.7 is described as this…

We continue to improve the experience in your Reader, and you can now mark posts as “seen” as well as view your total of “unseen” posts.

Okay, what does that mean? Why would I want to mark posts as “seen”? Does that send a notification that to the blogger who wrote the post that I’ve seen it? Here’s an example of what it looks like:I can also mark a post I’ve seen as “unseen.”So much for the old saying that once you’ve seen something you can’t un-see it.

I’m hoping that someone out there can explain to me what the purpose of marking a post as “seen” or “unseen” could possibly be.

And I’m going to contact the Happiness Engineers and link to this post and ask them if they can explain how this new “feature” improves the Reader experience, and, more important, why they’re focusing their efforts on seemingly unnecessary features and not on fixing that goddam bug!