SoCS — If It Ain’t Broke, Don’t Fix It

I’m a little confused by Linda G. Hill’s instructions for today’s Stream of Consciousness Saturday prompt. First, she says that the prompt is “last thing that broke/you had to fix.” But, then she goes on to say that we should “think about the word that best describes the last thing that stopped working for you and use that word any way you’d like.”

So are we supposed to write about the last thing that actually broke that we had to fix? Or are we supposed to use the word that describes the last thing that stopped working and write about that word?

For example, if the last thing that broke that I had to fix was my toaster, should I write about that broken toaster and what I had to do to fix it?

Or, since my toaster is old, should I write about the word “old” because it describes the last thing that stopped working?

Do you see my dilemma here? Well, I guess I’ll do both.

The last thing I broke was my hip when I fell off a ladder. What did I have to do to fix it? I had to have emergency surgery for a partial hip replacement and go through nine-months and counting of physical therapy to fix it.

What word would I use to describe falling off a ladder and breaking my hip? I think it would either be “careless” or “stupid.”

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.

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.

Broken


B78016A9-B71B-4159-91B2-AA991C1D4044There are days lately when I feel like I’m broken.

Days when nothing seems right and everything seems wrong.

Days when the very idea of getting up and out of bed is abhorrent.

Days when my body aches and my mind has stopped functioning.

Days when my shell feels cracked and my insides feel rotten.

Days when I wish the nightmare would finally be over.

And then there are days like today.

Days when the sun is shining and there’s not a cloud in the sky.

Days when I can’t wait to rise and shine and meet the world head-on.

Days when I feel as if all of my dreams will come true.

Days when I’ll be seeing you, hugging you, touching you, loving you.

Days when you fix my broken body, my broken heart, my broken soul.

Days when you put me back together again.


Written for today’s one-word prompt, “broken.” Image credit: Marisa04 at Pixabay.com

The Fix Is In

IMG_2641Isn’t it glorious when something works like it’s supposed to. As I noted in this post, yesterday’s WordPress one-word prompt was broken. I just checked and that prompt had 308 likes and 0 responses. Zero responses!

Today’s prompt, which is the word “glorious,” has, as I write this, 118 likes and 70 responses. So whatever it was that was ailing the prompt yesterday has been fixed today.

What once was broken has now been fixed. Isn’t that glorious?