Tag: Comments

Recycling?

~ Patrick O'Grady ~ 14 Comments
The DBR Axis TT and I went for a spin in the Elena Gallegos Open Space on Tuesday as the temps inched back into the low 40s.

Naw. That ain’t trash, waiting to be packed out. It’s just old, like its operator.

So don’t pack us out, for pity’s sake. Ain’t neither of us ready for the scrap heap yet.

Speaking of old trash and scrap heaps, I finally heard from the WordPress people about the comments issue, which seemed to have resolved itself to some degree after my last complaint on Nov. 22. Quoth WP:

The comment reply box has changed to the new box that adds the options of styling or layout changes using blocks. It cannot be disabled, it is the new default.

Fear not, your visitors don’t have to use the blocks, they can simply click into the box, and start typing.

This is the new “Reply” box as I have been seeing it lately.

A limited inspection of the process indicates that leaving a comment is once again fairly straightforward:

1. Place your cursor (or, depending upon your mood at the moment, “curser”) in the “Leave a Reply” box and start typing.

2. You will then be presented with the option of logging in using a WordPress account, Facebutt, or email (the latter method wants your email addy and a name; providing a website is optional). Select a login method.

3. You also are prompted to have posts/comments emailed to you. The buttons are off by default. Make another selection.

4. Hit the “Reply” button at lower right.

I switched laptops and launched Chrome to try commenting using an old email address. But I was not logged into the Gmail account I wanted to use and got a prompt saying so (O, buggah, etc.).

Rather than dive down that rabbit hole (usernames, passwords, and shit, O my!) I switched to Firefox to post my comment and saw it had me already logged in using my WP info.

I don’t have a Facebutt account so I couldn’t evaluate that option.

Anyway, that seems to be where we are at the moment. We don’t have to face that quadruple-decker “Reply” box with all the arcane symbols belonging to WP’s Block Editor (curse its name, yes). Just start typing and let ’er buck, cowpersons.

Anyone still having issues? Leave a note in commaaaaaaaaah ha ha ha ha ha ha ha ha ha. Sorry, couldn’t help myself.

No comment (yes, again)

~ Patrick O'Grady ~ 16 Comments
This way to the Egress?

We seem to have been detoured off the Infobahn and onto yet another long and winding washboard gravel road to Hell as regards what should be the simple process of posting a comment on the DogS(h)ite.

I first noticed the latest WordPress “enhancement” the other day while trying to comment on the Better Burque blog. Being logged into WP, I assumed — wrongly, as it turned out — that I could write my comment and post it under my nom de blog.

But when I wrote my little piece, then clicked the “Reply” button, nothing happened. Or so it seemed. There was no visual cue that the button had been clicked. My comment just sat there, like a fresh turd on a flat rock.

So I clicked the “Reply” button again and immediately got a popup that said something like, “Oops! Looks like you’ve already said that!”

And so I had. The comment had been posted, but not as me — as Anonymous, who seems to be everywhere these days, and mostly up to no good, too.

Anyway, I forgot all about it because I comment on the DogS(h)ite from the Comments tab in WP and never actually see the preposterous clusterfuckery that appears at the bottom of each post, the way you Little People do.

Nevertheless, there it squats, like a poison toad, a probe from the WP Block Editor that has infiltrated my Classic Editor environment, bent on mischief.

Now, I just viewed the blog using my backup MacBook and a different browser (Chrome) that was not logged into WordPress. So I got the full nickel tour of Whatthefuckopolis.

And what an ugly neighborhood it is, too. Frank Lloyd Wrong on the brown acid designing the Hotel California for a Wes Anderson movie.

It seems navigable, but I didn’t go through the entire process of logging in with an email address or my Google, Apple, or WP deets because I don’t want to get caught in some digital Doom Loop that drops me onto the Event Horizon just before everything goes sideways in orbit around Neptune.

I will ping the Happiness Engineers about it. There must be a way to return to the simpler days of commenting, before some engineer decided to go all carbon-fiber, hydraulic-disc and electronic-shifting on us.

Theme song

~ Patrick O'Grady ~ 13 Comments
The Wizards of WordPress deliver unto us from their Celestial Canale.

The Wizards of WordPress finally checked their Palantír and noticed they’d failed to respond to my feeble pleas for succor, or as some jaded customer-service types call it, “Sucker.”

But respond they finally did, yesterday. And thus, as your reigning Prelate of Punditry, I bear their scriptures to you, my congregation.

First, since the comments issue seems to affect different users (Mac, Windows, Firefox, Safari) in different ways, the duty wizard suggested that those of you experiencing technical difficulties “post in our public support forums to get help troubleshooting [your] setups.”

Adding a “modlook” tag to your post on forums.wordpress.com will add it to the staff queue for that team, quoth the wizard via email.

Now, I realize this may be a bridge too far for some of yis who are moved occasionally to rattle-can a little snark onto Your Humble Narrator’s virtual railroad trestle. And in any event, crossing it might not lead you to a brave new commenting world.

Because the duty wizard added that the the blog’s theme, like its operator, “is very old and no longer compatible” with many browser setups.

“There are more modern themes that still stay true to the simplistic aesthetic of Kubrick,” the wizard added, suggesting that I search WP’s theme park for a new one with tags like “blog,” “author,” “technophobe,” “senile old hack,” “gibbering eejit,” “Stone Age scribbler,” “nursing-home newsletter,” or “STFU.”

(Actually, the wizard only pitched the first two tags. But hey, it’s my blog and I’ll lie if I want to, lie if I want to, lie if I want to — you would lie too if it happened to you.)

Ordinarily when someone suggests “It’s not us, it’s you,” I snort and holler, “Boooooooosheeyit!” But I’m inclined to buy what this wizard is selling because I’m rocking some seriously old gear here and have been noticing my own technical difficulties doing bits of this, that, and the other in my journeys throughout the Innertubes.

I mean, c’mon: A 2014 MacBook Pro running macOS Mojave 10.14.6? Sure, 16 GB of memory and plenty of room yet on the old internal drive, but still, we’re talking Safari 14.1.2 here. That dog’s so old it won’t hunt WP’s theme park for some of the newer possibilities. Just staggers around the gate sniffing and pissing on the bars.

So, we may be looking at a prolonged period of “upgrades” here at Ye Olde Dogge Pounde. OS. Browser. WP theme. Etc. Get ’er up there on the lift, Skeeter. Sweet holy motherfuck, what we got here? Git a bucket under that! And fetch my .22 wheelgun, something’s built a nest in there. Do Duck! City woodrats have eight eyes?

My plan, such as it is, is to experiment with new themes using an old blog, rather than risk the Main Attraction, which goes all the way back to November 2008. I keep a couple-three shuttered shops in the old unreal-estate portfolio just in case this sort of nightmare ever reared its ugly head(s).

More as I learn it. Please continue to hold. Your call is important to us. A Misery Engineer will be with you shortly. Your wait time is currently …. beeeeeeeeeep.

No comment, part 3

~ Patrick O'Grady ~ 30 Comments

OK, here’s the latest.

I haven’t heard back from the Wizards of WordPress in a week, and I’m fixin’ to tug on their beards again.

Any of you folks still having trouble commenting?

If you can’t reply here, please do so via email. If you don’t know my email address, just click the picture of Il Fattini at right and scroll down.

Thanks in advance, and now we return you to the blog, which is already in progress,

No comment, part 2

~ Patrick O'Grady ~ 25 Comments
Yo, how’bout you log in to this right here, hey?

A WordPress “happiness engineer” and I have had one exchange of views about the comments issue, and I am eagerly awaiting round two.

In the meantime, if you continue to have problems sounding off in this space, the WPHE’s advice is to:

• Clear your browser cache and cookies.

• Make sure Javascript is enabled.

As for me, I recommend trying a variety of browsers. I was able to comment on the DogS(h)ite using the Mac versions of Firefox and Chrome on a 2014 MacBook Pro running the Catalina OS.

Some of you have noticed that the “Leave a Reply” box looks a little different lately, and the WPHE acknowledged that WP “is constantly updating and improving its features (emphasis mine), so it’s possible that recent updates could have affected the appearance or functionality of the comment box.”

O, indeed. “In my Father’s CMS there are many updates,” as the Good Book tells us.

Now, I’m just spitballing here in the absence of evidence or expertise, but it’s possible that my insistence on using WP’s Classic Editor instead of its beshitted Block Editor — curse its name, yes — may play some role here.

Or it may be that the theme I use, the venerable Kubrick, has long since been “retired” and is no longer supported properly. Chances are it’s just gathering dust and being “updated and improved” by mice in the bottom drawer of an Army-surplus metal desk down in storage room B. There may be a Swingline stapler on the desk, right next to a box of matches.

Lotta strands in old Duder’s head, man. And they’re not all plugged into the proper sockets. More as I hear it. Meanwhile, keep those cards and letters coming, and don’t touch that dial.