You could rescue me from this torture.
You could take me to the garden.
We could assimilate
All that nature has to offer.
You have the power
To obliterate my pain.
But you won’t.
In fact, you seem amused by it.
You’re a sadist.
Written for these daily prompts: Ragtag Daily Prompt (rescue), Fandango’s One-Word Challenge (torture), Jibber Jabber (garden), Your Daily Word Prompt (assimilate), Word of the Day Challenge (obliterate), and The Daily Spur (amused).
The good news is that it’s June 16th and WordPress has not forced me to use its Block editor that it said it was switching to as of June 1st. That’s right, I’m still able to use the Classic editor without having to jump through extraordinary hoops to do so. Yay!
But something weird is going on. I compose my posts on my iPhone at either Safari or Chrome using WordPress.com and the visual tab of the classic editor.
I’ve been doing it this way since my return to blogging in May of 2017 after a two year hiatus. And it has worked perfectly.
Recently, though, there has been a fly in the ointment, so to speak. As I compose my posts, I periodically preview what I’ve written so far to see what it will look like when I publish it. I’ve noticed that for the past week or so, even though everything looks fine in the visual editor, when I preview the post, random lines show up in a much smaller, slightly lighter font than the rest of my post, as in the example below from a post I was working on yesterday.
I’m not exactly an HTML expert, but I am familiar enough with it that I will occasionally go to the HTML tab to fine tune something that doesn’t quite look right when I preview my post. And that is when I see this line of HTML code inserted into my post:
For some reason that line of code is being randomly inserted into the HTML on my draft posts and it changes the way my posts look. I have to manually delete that strange line of HTML code in order to keep the fonts consistent throughout the post.
I’m not sure if this is an iPhone problem, a browser problem, or a WordPress.com problem. Or could this be a deliberate act of sabotage on the part of the WordPress happiness engineers to punish those of us who have resisted the move to the Block editor?
Is anyone else having this happen on your posts? Is there an HTML expert out there who can explain to me what causes this and how to keep it from recurring? I’d appreciate any help I can get.
Welcome to June 16, 2020 and to Fandango’s One-Word Challenge (aka, FOWC). It’s designed to fill the void after WordPress bailed on its daily one-word prompt.
I will be posting each day’s word just after midnight Pacific Time (US).
Today’s word is “torture.”
Write a post using that word. It can be prose, poetry, fiction, non-fiction. It can be any length. It can be just a picture or a drawing if you want. No holds barred, so to speak.
Once you are done, tag your post with #FOWC and create a pingback to this post if you are on WordPress. Or you can simply include a link to your post in the comments.
The issue with pingbacks not showing up seems to have been resolved, but you might check to confirm that your pingback is there. If not, please manually add your link in the comments.
And be sure to read the posts of other bloggers who respond to this prompt. You will marvel at their creativity.
This, That, and the Other 