A month after deciding to start using WordPress blocks before their classic user interface became one with Nineveh, Tyre and rotary telephones — I don’t have the usual Saturday post ready.
The good news is that I’m more comfortable with WordPress blocks than I’d feared.
And, more good news, I’ve finally finished updating this blog’s widgets.
The frustrating news is that updating, fixing and in some cases removing widgets took all this week. I finished the last (I hope) of that task Friday afternoon.
The process would have gone faster if the WordPress ‘blocks’ user interface didn’t take between ten minutes and an hour to load all of its nifty new ‘blocks’ widgets editing page.
The page itself, along with several dozen ‘you got problems’ messages, came up promptly. What sometimes never loaded were the little — dialog boxes? block bits? — that represented ‘pre-block’ widgets.1
That was then, this is now. The nifty new ‘blocks’ widgets editing page now loads with no more than up to a half-dozen ‘you got problems’ messages. And, thankfully, most of the little — dialog boxes? block bits? — load without giving me time for a coffee break.
Now some definitely not-so-good news. Although it could be worse.
A Catholic Citizen in America is now on a Hypertext Transfer Protocol Secure (HTTPS) domain — which I gather is a good thing.
However, anyone who had been using this blog’s RSS feed stopped getting new content the moment that “https” thing went into effect. After a little checking, I’ve found no way of restoring A Catholic Citizen in America’s RSS feed.
And I’m pretty sure that RSS and https won’t work together. Which may be part of why HTTPS is so much more secure, and that’s another topic.2 Topics.
Checking in each Saturday, or however often seems convenient, is one option for seeing new content here.
So is getting notifications via email. I really wish email notifications were easier to find. And that alternatives — I’ll get back to that.
(Note: This is an image of the comment form, not the real thing.)
Right now, the “Notify me of new comments via email” and “Notify me of new posts via email” checkboxes are on the comment form. At the bottom of the comment form.
And those “Notify me of new…” checkboxes will not appear unless you make a comment, or at least click in the “Enter your comment here” box.
I don’t know what would happen if someone clicked a “Notify me of new…” with a blank “Enter your…” box, and then clicked the “Post Comment” button. [Update July 16, 2022 – apparently there must be something in the comment box, or the ‘post comment’ button won’t work.]
I’d prefer having more options for folks who want email notifications or something like the now-unavailable RSS feed.
Make that acceptable options. I found widget-using software that promised easy handling of email lists.
Easy, I got the impression, for folks who see no problem with spamming their readers.3
I could be wrong about ‘Spamalot Services’ — catchy name, that, but fictional.
Like I said, I could be wrong about the software I’m not using. But if I’m right, that’s emphatically not what I want to do.
So that’s what I’ve been doing this week. Working on widgets. Mostly.
I’ve also been reading Kramer’s “History Begins at Sumer,” enjoying a visit from son-in-law and granddaughter; and plan to take it easy this weekend.
And hoping that next week I’ll have something about science, history, Faustus — or pretty much anything other than another ‘technical’ report ready
Last week’s ‘Saturday’ post, and earlier ‘technical’ stuff:
- “History, Viewpoints, Narratives and Ancient Rome“
(July 2, 2022)
- “Learning Something New: WordPress Blocks“
(June 7, 2022)
- “I’m Back! — So are Comments and ‘Likes’“
(May 6, 2022)
- “I’ll be Back, or, Resolving Technical Issues (Maybe)“
(May 3, 2022)
- “Norbert Nerdly Rides Again: Keyboard Concerns“
(April 2, 2022)