For Those Who Blog Using an iPhone

As most of you who follow my blog know, I use my iPhone for blogging. Not a laptop computer, not a desktop computer. An iPhone 8 Plus with a 5.5 inch screen. You may also know that I’m not a fan of the WordPress block editor, which is clearly not designed to use on the relatively small screen of a smartphone.

This post is about using an iPhone for blogging and about my disdain for the block editor. So if you are not interested in reading my thoughts on either of those topics, I give you permission to move on.

The good news is that, even though WordPress has retired its classic editor as it is forcing all of us to embrace its clunky block editor, there is a setting on the WordPress iOS app that allows us iPhone bloggers to default to the classic editor (or a version of the classic editor that I call “classic lite) when composing or editing a post using the iOS app.I’ve been worried that, as it did with the classic editor on, the decision makers at WordPress would eventually remove the option to use the classic editor in the iOS app. So, in a resent exchange I had with one of the WordPress “happiness engineers,” I wrote:

I don’t use, or want to use, the block editor or the classic block within the block editor on my iPhone. Please tell me that WordPress is going to continue to support the classic editor in the iOS app.

I suppose, in my naivety, I expected a response like, “Not to worry, Fandango, we’ve got your back.” But instead, this is the response I got:

There are no plans to continue to support the classic editor in the app or even in a web browser. It’s an editor that is being depreciated. Our hope is that the Classic block bridges the gap of the old editor to the new, while you learn to use the new editor!

So much for having my back, WordPress.

Drop Cap

I read with interest a post today from Frank, aka PCGuy, who was talking about the ability to incorporate a feature called the “drop cap” on his posts. Frank wrote:

With all the frustration that has come with the recent changes that has made to their blogging platform, I though it might be good to shed a little light on a good thing that I have discovered. It’s small, but it makes a big difference in the visual appearance of your text. If you take a look at the settings when you use the paragraph block in the new Gutenberg [block] editor, you’ll see an option for a drop cap.

As Frank noted, this ability to incorporate the drop cap functionality is accessible in the paragraph block within the block editor.

Oh well, I thought, that’s too bad because I hate the block editor and refuse to use it. So I guess I’m SOL if I ever wanted to incorporate a drop cap into my posts.

But then Frank pointed out that having to use the block editor is not entirely accurate. He wrote that one can accomplish inserting a drop cap using the classic editor by leveraging a simple HTML command, which Frank was kind enough to share with his readers:

<p class=”has-drop-cap”>

Now I can honestly say that I never gave much thought to using the drop catch functionality on my posts, but after reading Frank’s post, I figured I’d give it a try using the classic editor available in the WordPress iOS app for the iPhone. So I wrote this paragraph:

“This is a test to see if, within the classic editor on the iPhone’s WordPress iOS app, I can use the Drop Cap functionality without having to use the block editor.”

Then I copied that brief paragraph, selected the “Switch to HTML Mode” in the iOS app, and surrounded the “T” at the begging of the paragraph with the HTML expression that Frank offered. In HTML, here’s what it looks like.

<p class=”has-drop-cap”>T</p>his is a test to see if….

Then I pasted that edited paragraph below and this is what it looks like in the preview mode after I added the HTML to that line.


his is a test to see if, within the classic editor on the iPhone’s WordPress iOS app, I can use the Drop Cap functionality without having to use the block editor.

Pretty cool, huh? That said, I may or may not use the drop cap functionality in future posts. But thanks, Frank. It’s alway fun to learn how to do something on my blog that I didn’t know how to do before, especially when I can do it without using the goddam block editor.

SoCS — Old and New

For today’s Stream of Consciousness Saturday, Linda G. Hill wants us to explore “new/old” and to use either or both of the words — “new” and “old” — any way we’d like.

Typically, one might think of new and old to be opposites, where “new” has a positive connotation and “old” has a negative one. For example, there’s that cool new telephone you bought to replace your crummy old one, that new car that you got after trading in your old car, that new house you moved into after you sold your old house, or that hot new chick you’re seeing after you divorced your old lady.

But “new” and “old” are not always synonymous with the good or bad connotations often ascribed to them. I’m an old man, but after I retired I had to try to reinvent myself and to become a new man, which was a necessary and good thing to do. Now if only I could figure out how to reinvent myself from an being an old man to being a young man.

And there’s the “out with the old, in with the new” philosophy that seems to be embraced by so many these days. New and improved is not necessarily better than old and reliable. And yes, that’s a none-too-subtle jab at WordPress for having shitcanned the good old classic editor and replacing it with that awful new block editor, forcing some of us to decide if we even want to continue to blog on WordPress.

And with all that said, it’s time to greet the new day and to hope, with all the crap that is swirling around us, that it will be no worse than the old day was.

Have a nice Saturday, folks.

WordPress is FOWCing with Fandango…Again

As most of you know

  1. I blog using my iPhone
  2. I hate the block editor because it sucks on an iPhone

And, as most of you also know, I host a number of prompts, including my daily FOWC with Fandango prompt. What I do with this (and my other prompts), is

  1. log on to
  2. use the classic editor version on the wp-admin site
  3. copy the latest published or recently scheduled post for the new prompt post
  4. that opens up the post to be copied in classic editor
  5. make the necessary changes for the new prompt post in the classic editor
  6. save and schedule the updated post for the appropriate day and time in the classic editor

But as of today, when I go to the wp-admin site on my iPhone and try to copy an existing post that was published using the classic editor, it opens up the copied post in the goddam fucking block editor. At least it does on my iPhone — I haven’t tried it yet on my laptop.

And as of today, even if I’m logged on to wp-admin, when I go to add a new post, it opens up the block editor with no option to use the classic editor.

I’m going to reach out to the WordPress happiness engineers, but I’m pretty sure I know what they’ll tell me: “Too bad, so sad.”

But I’m telling you folks, this may be the proverbial straw that broke the proverbial camel’s back. If this is the way it’s going to be from now on, I may stop posting my prompts. Hell, I may stop posting altogether.