Fandango’s Flashback Friday — April 16

Wouldn’t you like to expose your newer readers to some of your earlier posts that they might never have seen? Or remind your long term followers of posts that they might not remember? Each Friday I will publish a post I wrote on this exact date in a previous year.

How about you? Why don’t you reach back into your own archives and highlight a post that you wrote on this very date in a previous year? You can repost your Friday Flashback post on your blog and pingback to this post. Or you can just write a comment below with a link to the post you selected.

If you’ve been blogging for less than a year, go ahead and choose a post that you previously published on this day (the 16th) of any month within the past year and link to that post in a comment.


This was originally posted on April 16, 2018.

Pep Talk

John knocked on his boss’s door. “Excuse me, Al. Do you have a minute?”

“Sure,” Al responded. “Come on in and have a seat.”

John sat down in a chair across the desk from Al. “I’ll get right to the point, he said. “In my written review you wrote that I need to crank it to eleven. What did you mean by that?”

“John,” Al said. “It means that it’s time for you to turn up the volume.”

John looked confused. “Turn up the volume, sir?”

“You know what I mean, John,” Al responded. “It’s time to put the pedal to the metal.”

“The pedal to the metal?”

“John, you know what I’m saying,” Al said. “You need to give it 110 percent.”

“Are you suggesting I’m not doing all I can for this job?” John asked.

“I’m just saying that it’s better to ask for forgiveness than it is to ask for permission, John,” Al said. “It’s time for you to shoot for the moon, to sing like no one is listening.”

“I see,” said John.

“Good,” said Al, “because you know that you miss 100 percent of the shots that you don’t take. Son, you need to make hay while the sun shines. When opportunity knocks you need to answer the door.”

“Yes, I see what you’re getting at,” John said, trying hard not to roll his eyes.

“Good,” said Al. “Now go out there and make it rain, my boy.”

John went back to his cubicle and started drafting his resignation letter.


Written for today’s one-word prompt, “crank.”

Truthful Tuesday — R.I.P.

Frank, aka PCGuy, has published another one of his Truthful Tuesday posts, only this time, Frank has announced that he’s discontinuing this popular prompt. Frank writes that he has become quite disenchanted with WordPress.com, and that he will be looking for alternatives to keep blogging, alternatives that will fit his sensibilities and relatively nonexistent budget.

I can definitely relate, Frank. Between the block editor and unfixed bugs, I’m frustrated with WordPress as well. Still, it’s tough to see a fellow blogger end a popular prompt as he contemplates his next move.

All the best, Frank. Hang in there.

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.

Truthful Tuesday — Playing With Blocks

Frank, aka PCGuy, has published another one of his Truthful Tuesday posts, and this week Frank wants to know if we enjoy playing with blocks. He wants to know…

How have you adapted to the complete removal of the classic editor from WordPress.com? Are you managing to get by with the block editor, or are you finding it difficult to want to blog now that your trusted tool is no longer available?

Oh man, don’t get me started on the block editor. I have been very vocal about how much I hate it. The classic editor was fine. It was unobtrusive and it enabled writers to focus on writing, not on mechanics. But, for whatever reason, the folks at WordPress decided to put all of their money (and our money, for those of us who have upgraded) into the block editor.

The good news is that several bloggers have posted a way to continue to access the classic editor on wordpress.com. And that’s great for those who use their desktops or laptops to blog.

Unfortunately, most of my blogging is done from my iPhone. As of now, the option to use the classic editor is still available on the WordPress iOS app for the iPhone, although WordPress is threatening to take that option away at some point in the near future. So I may have to try to embrace the iOS version of the block editor.

Preparing for that day, I’ve been using the block editor on my iPhone for about a quarter of my posts. It’s okay, but I feel like I have way less control. And then, when I look at the HTML code, there is so much more of it with the block editor than there is with the classic editor.

In order to get the final post to look the way I want it to, I often give up on the block editor and revert back to the classic editor. And then I have to go into the HTML editor and strip away a lot of that weird code. As a result, it has taken me two to three times longer to publish a post using the block editor than using the classic editor.

So, bottom line, I have mostly stuck with the classic editor mode on the iOS app.

Now to answer Frank’s question, if WordPress dumps the classic editor in the iOS app, I’ll either have to abandon blogging from my iPhone and blog exclusively from my laptop, try to make do with the block editor on my iPhone, or maybe just call it a day and stop blogging.

I guess I’ll make that decision when the time comes.