Hurry Up and Wait

I was excited the other day when I saw that WordPress had pushed out an update to its iOS app for the iPhone. I was sure that version 16.1.1 had a fix to the Reader issue that by now you are no doubt tired of hearing me whine about.

After it installed on my iPhone, I opened the app, went to my Reader, and clicked “Visit” on a post that I had been unable to like or comment on after the previous update. Unfortunately, even with this new update, I was still unable to like or comment. Bummer.

So I sent a message to the happiness engineers.

I was disappointed yesterday, after installing version 16.1.1 of the WordPress app for iOS, that the issue with the WordPress Reader that surfaced when version 16.0 was installed, and for which I’ve been exchanging messages with various happiness engineers since November 3rd, is still unresolved. I hope your team will be releasing a fix for this issue in short order.

The response I got essentially reminded me that Rome wasn’t built in a day. Here’s the answer I received:

We understand this is frustrating. But even with high priority issues, it does not mean the fix will be released in the next update. Some things take longer to fix than others. We don’t have an ETA on this one yet, but our developers are working on it. We appreciate your patience and apologize for the inconvenience.

So I guess I’m in a hurry up and wait mode and the happiness engineers at WordPress will be taking their sweet time getting around to fixing the issue. As the old song says, they’ll be coming ’round the mountain when they come.

A Breakthrough…Maybe?

I have been communicating with the WordPress Happiness Engineers nearly every day since November 3rd when the latest version of the WordPress app for iOS was installed on my iPhone. But so far our communications have not yielded any positive results. Up until today, maybe.

I once again did my best to explain what the issue is with respect to not being able to “like” or comment on some other bloggers’ posts from the reader on my iPhone. I wrote…

Every post where the site’s address does not include “.wordpress.com” has this problem and every site where the address does include “.wordpress.com” does NOT have this problem. This problem surfaced ONLY after version 16.0 of the iOS app was installed on my iPhone. There were no such problems before the update. So it’s pretty clear that whatever enhancements that were made to the reader in version 16.0 triggered the issues.

This time the response I got did not cite user error as the cause of the problem or blame it on my phone’s browser. In fact, the response I got was this…

Thanks! That is very helpful to try and replicate this problem. I’m sharing this with the rest of the team and we’ll jump into testing right away. As soon as we have an update we’ll keep you in the loop 🙂

So maybe, just maybe, a fix is in the works in the near future. Maybe.

In the meantime, if your blog does not have “.wordpress.com” in its address, I’m still unable to “like” or easily comment on your posts. Hopefully the issue that’s causing the problem will soon be rectified. Maybe.


Image credit: peggy_marco at Pixabay.

The Monday Peeve — It’s All About the URL

Through her The Monday Peeve prompt, Paula Light invites us to vent, to let off some stream, to get something off our chests. This week, my peeve is about troubleshooting. This is something the WordPress Happiness Engineers don’t do. In fact, whenever we are having an issue with WordPress, they seem to make us do all of the troubleshooting on their behalf.

Ever since version 16.0 of the WordPress iOS app was installed on my iPhone, I have had problems with being able to “like” and to comment on some (but not all) posts I visit from my reader or even from my Notifications. I first wrote about this apparent bug in the latest release of the iOS app here. I have been going back and forth with the WordPress Happiness Engineers on these issues for the past week and, so far, they haven’t come close to coming up with a resolution. Basically they keep asking me to try this or to try that to see if anything I try can resolve the problem.

Yesterday, I got a response from WordPress that said…

Unfortunately the activity logs you sent aren’t telling us much on what might be causing this issue. Can you share the URLs of a few posts/sites this issue is occurring on so we can see if this allows us to narrow down a possible cause.

So I, once again, did what they asked. I provided the URLs of six blogs where I can’t “like” the posts and where I can’t comment at all or can’t comment without entering my name, email address, and my blog’s URL.

Then I provided the URLs of six blogs where I can both like and comment, just like I used to be able to do before version 16.0 of the iOS app was installed on my iPhone.

EUREKA!

I discovered something that apparently the Happiness Engineers at WordPress didn’t even think about. Here’s what I wrote.

AH HA! As I was going through this exercise, I just noticed that the blogs that have “.wordpress.com” in the URL work fine, just as they used to before Version 16.0 was installed. But the blogs that just have the blog name without “.wordpress.com” in the URL are the ones that don’t work.

My blog’s URL is https://fivedotoh.com. It doesn’t have “.wordpress.com” in the URL. I just went to my reader on my iPhone and visited my own post and guess what? I can’t “like” my own post or comment on it without entering my name, email, and website. MY OWN POST!!!

So, it seems that the way to resolve this problem is to find out why blogs that contain “.wordpress.com” in the URL work fine in the Version 16.0 reader and notifications, but those without “.wordpress.com” in the URL, like my own blog, do not. I think if you can figure out why that is happening and how to fix it, you will have resolved this issue.

And that, my friends, is what has me very peeved this morning. Maybe I should apply for a job as a Happiness Engineer.

User Error

I still cannot “like” or comment on many of your posts when I access them from my reader on my iPhone. I’m sorry, because I do read your posts and I can “like” them if I read them in the reader view, which is not ideal because in reader view, much of your formatting is not displayed as it is when I view them on your site.But now, after the latest update to the iOS app was installed on my iPhone earlier this week, when I actually click on “Visit” to go to your site from within the reader, not only can’t I “like” them, I can only comment on your posts if I enter — each time — my name, my email address, and my blog’s URL.And that’s a real pain, since the app should know who I am without my having to reenter my credentials.

Well, the Happiness Engineers at WordPress have gotten back to me on what appears to be a bug in the latest version of the app for iOS. I have been exchanging messages with various “Happiness Engineers,” and it has come down to being told that “the issue you’re experiencing seems like it’s not an app issue.” Oh, I get it. It must be a user error. I must have broken something when the update to the app was automatically installed onto my iPhone one night when I was asleep. Yep, it’s not them, it’s me.

Bullshit!

I wrote back and said…

This was NEVER an issue within the WordPress iOS app on my iPhone until Version 16.0 was installed. I could “visit” posts from the reader of those who commented or linked to my posts and the app knew who I was and that I was actively logged on to WordPress. Thus, I could like their posts and I could post comments without having to enter my name, email address, and my blog’s URL each time.

But with the latest update, that is no longer the case. In your release notes for version 16.0 of the iOS app, you specifically pointed out that the reader was “redesigned” and “refreshed” to include “a number of changes….” Since the issue I’m having in the redesigned and refreshed reader didn’t occur before you redesigned and refreshed it, I cannot accept your conclusion that it’s not an app issue. What else can it possibly be? Up until the update to the app was installed on my iPhone, I wasn’t experiencing this issue on the app at all.

Please escalate this issue to your most tech savvy gurus who are responsible for the iOS app. I’m very unhappy and upset and between forcing the damn block editor down our throats and this latest issue in the “redesigned and refreshed” reader, blogging on WordPress is becoming more of a burden than an enjoyable and rewarding experience.

FIX THIS!

I’ll let you know what happens, but I’m not holding my breath. In the meantime, I once again apologize for being unable to like and comment on many of your posts.

FUBAR

Warning: this post is all about how the latest update to the WordPress iOS app for the iPhone broke my reader. If you have no interest whatsoever in reading about this, feel free to move along.

So I know that in my last post I said that I was going to take a break from posting for a while, but trying to deal with this technical issue with WordPress and its latest update to the WordPress iOS app is keeping my mind of of politics. And all things considered, that’s a good thing.

I’ve been exchanging messages with a few Happiness Engineers to see if they can fix what they broke in the iOS update. When I first opened a ticket and explained the issue, one of the response said this:

One thing we’ve noticed is that you’re currently logged into 402 sessions (meaning logged into WordPress.com in 402 places — devices, browsers, etc). We’re not sure yet if this is the underlying issue for you not being able to like/comment on posts, but logging out of all the current sessions may help.

What? So here’s how I responded:

I don’t understand how it’s even possible for me to be logged into WordPress 402 times. I do use four different browsers at various times — Safari, Chrome, Firefox, and Duck Duck Go — and I tried on all of them last night to go to the reader and like and/or comment on other bloggers’ posts. I wasn’t able to. I’m going to log out of all browsers and log out of the iOS app now.

And then I got this response:

I’ve reviewed your account and see that the account is still logged in to 400 sessions. Could we log you out all of those sessions so we can see if that is contributing to this problem? Please confirm that you would like for us to try that and we’ll log out all of the sessions from here.

To which I responded:

Yes, please log me out of the 400 sessions. And please explain to me how it is even possible to be logged on to 400 wordpress.com sessions at one time.

I went back and looked at the notice that came with the WordPress version 16.0 update and saw this.Then I wrote back to the Happiness Engineers and said this:

As a point of clarification, I can both like and comment on other bloggers’ posts if I stay in the reader view. It’s only when I click “visit” in the reader and go to the bloggers’ actual posts through the reader that I can’t like or comment on their posts when accessed that way. I noticed that, in the 16.0 update notes, you made some changes to “Refresh the Reader” and to improve the experience, but whatever changes you made to refresh the Reader certainly screwed up my ability on many of the blogs I follow (but not on all, for some reason) to like and comment on them when I click on “visit.”

Anyway, I’m curious if any of you out there in the blogosphere who are more technically savvy than me can explain to me how it’s possible to be concurrently logged into 400 WordPress sessions when all of my browsers have been closed.

Okay, I’m going to fix myself some lunch now. If I hear back from the Happiness Engineers, I’ll let you know.