Block editor

Once more around the block.

Some of yis have noticed that commenting via Safari seems to have been restored, all praise to Cthulhu, may Its tentacles grow ever longer.

Last night I heard from a code wrangler at Automattic who advised thusly:

This issue has been forwarded to our development team. I cannot give a time frame on when the issue will be fixed but a workaround is to disable “blocks in comments.”

Huzzah, etc. Remember the last time we had trouble with comments? How it forced me into finally abandoning the Classic Editor for the Block Editor, and changing themes to boot?

Yet now, here we are again. Because not only are comments buggered without the workaround, pending a solution from the development team, it could be that the advanced age of my current “new” theme, Penscratch 2, may be part of the problem.

Thus, a tip of the Mad Dog Safari Hat goes out to our own Steve O’, who suggested as much in — wait for it — comments.

Meanwhile, cheers to Jason the Code Wrangler for kicking this thing up the chain of command and recommending the workaround, which works.

While we await the Wisdom from On High I may slap a new coat of theme on an old blog and ask you Safari users to try commenting there. Steve O’ and Pat O’B have been able to comment on this junkpile, which runs on Independent Publisher 2, but I think that theme is a tad long in the tooth as well.

Is this thing on?

While we await the wisdom of the WordPress Wizards, SAO — one of our longtime readers who can still post comments — suggests that the Dog Blog’s theme, Penscratch 2, may be at least part of the problem.

Penscratch 2 is an old theme — not as old as its predecessor, Kubrick — but still, plenty of white hair in its ears and a stoop to its bony shoulders, plus it seems to have forgotten where it left its keys to the comments. Also, it may have shit the bed.

So, while we wait — and wait, and wait, annnnnnnnnnnnd wait —I need someone who is still unable to comment using Safari, DuckDuckGo, or whatever to try adding a comment to the most recent post, “Age limits,” at this unused blog, which runs the Independent Publisher 2 theme.

Thanks in advance. More as we learn it.

Baking with WordPress

We had apricot crisp for dessert last night. WordPress says you lot need cookies.

OK, I finally heard back from the Wizards about the comments issue. They advise thusly:

Please ask your readers to check if third-party cookies are enabled. If not, enable them. Here are the steps you need to follow: In the Safari app on your Mac, navigate to Safari → Preferences → Advanced, then unselect “Block all cookies.” Here is our guide to check and disable/enable third-party cookies.

I’ve asked whether this is a new thing, since this is the first time the comments issue has been so widespread. More as I hear it.

So, yeah. If anyone wants to give that a go, have at it with my compliments. In the meantime, if you have fresh intel, new questions, or just want to vent, you can reach me at maddogmedia (at) the Fabulous GeeMail (dot) com.

Open mic

Our lines are open.

We didn’t watch the “debate” last night, so I don’t have any personal observations to add to this morning’s raving, keening, caterwauling, hair-pulling, wailing, finger-pointing, and general post-shitting-the-bed cacophony.

So consider this an “open thread.” Got any thoughts? Lay ’em on us in comments. Our operators are standing by.

A new dawn

In the pink? We certainly hope so. …

A’ight, y’all, buckle up, ’cause here we go.

I launched the new theme and the Block Editor (curse its name, yes) because like any good test pilot (and many more bad ones) I got tired of kicking the tires and decided to light the fires.

I expect we will find a few bugs in the bird as we tumble along, but here’s hoping we wind up with the cockpit on top and the wheels on the bottom.