Nothing to see here, folks; move along, move along. I’m just fiddling with the controls to get a handle on how many changes to the posting process WordPress slipped past me whilst I was otherwise occupied.
More as I learn it.
Meanwhile, for any of you who have had comments drift off into the ether, fear not. I’ll begin checking the spam folder a couple-three times a day.
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.
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.
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.
¡Basta ya! I embarked on a news diet yesterday. As in “fasting.”
Throughout the long Fourth I consumed exactly zero news, save for checking the weather to see if it was suitable for the healthy outdoor exercise.
And really, I could’ve just stepped outside for that.
But still. Shit.
The media had been keening without letup at a pitch that made an Irish wake look like sitting zazen. The Internet is said to be bottomless, the way a cup of joe used to be, but they came perilously close to filling the fucker up.
The fans in my 10-year-old MacBook Pro were approaching a Boeing level of failure. Every hot take a platter of steaming horseshit, smack in the gob. In my Father’s Bistro there are Many Dishes, I mused blasphemously. I sure as hell don’t have to eat this shit.
So I pulled a Level One Roberto Duran: “No más, no más.”
As mentioned in the previous post, yesterday I took my coffee on the couch, not at the desk. After breakfast Herself and I went for a short trail run. I followed that up with a 90-minute ride.
Then I set a loaf of bread to baking, poured the fixings for Sarah DiGregorio’s chipotle-honey chicken tacos into the Crock-Pot, argued with the Voices in my head about which of our many subscriptions we should cancel, entertained Miss Mia Sopaipilla, and served up the grub.
The three of us dined in front of the TV, streaming a couple episodes of “The Bear,” season three. (Spoiler alert: There was less hollering, even when Sugar was in labor.)
Afterward we joined the neighbors for their annual fireworks extravaganza in the cul-de-sac. No flyers or boomers, just ground-level sparklers and sizzlers. But an enjoyable tradition nonetheless.
One of the grandkids was leaping and cavorting throughout, trying to grab a handful of smoke, as grandpa performed his pyrotechnical wizardry. I caught my share of the exhaust while sitting down, in my clothing, eyes, and windpipe, and both Herself and I had to hit the showers afterward to hose off the residue of whatever those wily foreign devils put in their whizbangs.
The Republic I left to its own devices. I expect there was no shortage of counsel, and plenty of fireworks, too.
• Meanwhile, a housekeeping note: If any of you have tried and failed to post a comment recently, and you are using an Apple device, the problem may reside with the Safari browser. Herself was able to comment from an M1 Mac Mini using Firefox. I’ve pinged the WordPress people and will get back to you with whatever they have to say. But in the meantime, you might try using another browser to make your voices heard.
Mad Blog Media 