WordPress Block Editor considered harmful

The drop cap that starts this paragraph is something I could not have readily done in the Classic Editor here at WordPress.com, so I hope everybody reading this understands that I’ve spent some time looking for upsides to the Block Editor that has replaced it.

But those upsides still look scarce. Five months after WordPress.com anointed the Block Editor as the new default–and well over three years after this project’s debut–I still find basic tasks more difficult in the Block Editor than in the now-deprecated Classic writing interface. Four examples:

  • Inserting an inline image with text wrapped around it, as seen at right, apparently requires a detour to a separate block menu in which you reduce the image’s size, followed by a click on a menu to right-align the image. In the Classic Editor, those options sit in the dialog to select an image from the Media Library.
  • There’s no way to indent text outside of making it part of a bulleted or numbered list. This one sticks in my craw a bit: I told two WordPress representatives this was a problem after they gave a presentation at least year’s Online News Association conference, and they seemed to agree that indenting was a legitimate formatting tool.
  • This may be more of a bug than a design decision, but when I right-click on a link in Safari and paste its address into the Classic Editor, the link appears in a post as a complete hypertext link under the linked page’s title. In the Block Editor, pasting yields the address of the link, leaving it to me to copy its title and then turn that into a link.
  • The addition of a menu option to switch between editing and selecting modes, as if I were back into learning desktop publishing on Aldus PageMaker in 1991, allows for the chance to realize I clicked my way out of revising whatever I’m writing.

I think I understand where WordPress is going with this. The Block Editor offers a lot more options to embed different types of content, as seen in the screengrab above, and for bloggers looking to mash up their media, I can see why that would make sense. I also have a lot of faith in WordPress, having picked this platform instead of keeping my Web home on Facebook real estate and remaining convinced of the soundness of that decision.

Plus, speaking as a long desktop-publishing geek who may still have some muscle memory of PageMaker keyboard shortcuts: Yes, drop caps are cool.

But from my words-first perspective, the Block Editor makes the everyday writing here a little harder. And since indents are a basic element of the weekly-output posts I’ve been writing here since the fall of 2011, sometimes it makes my usual habits impossible.

I can still switch to the Classic Editor at the start of or halfway through a post, so I’m not doomed. But I worry that at some point, its deprecated status will lead to it being deleted. Will that point arrive before WordPress’s developers can get this editor to interface parity with its predecessor? Please wish me luck.

A fix for strange search results

Something looked broken with Web search on my computer yesterday, and it took me only about 18 hours of detours to figure out the problem. To spare you all the trouble of repeating my troubleshooting, here’s how things worked out.

search redirect network activityEverything started when I was doing a routine search for a post I’d written last winter on CEA’s blog. I clicked on Google’s link, saw a random address appear and then another, and found myself looking at a sketchy page with ads for some casino instead of my analysis of exemptions to the Digital Millennium Copyright Act’s anti-circumvention provisions.

My first thought–both frightened and angry–was that I’d finally gotten hit with a virus like DNSChanger on my own computer. But the same hijacked search happened in another Mac and on the Chromebook I’d just reviewed.

Maybe my wireless router had gotten compromised somehow? I had covered one reader’s experience with that two years ago, and my fellow tech journalist Glenn Fleishman (I’d say he’s forgotten more about WiFi than I’ll ever know, but he forgets nothing) thought that was likely too.

But the router had nothing amiss with its domain-name-server settings. Meanwhile, doing the same search in the browser on an AT&T Android phone (another recent review) didn’t yield any spurious results. Two replies on Twitter also suggested this issue might be specific to Internet providers.

My last move before getting distracted by our daughter was to try the same search on other sites. At Bing, the result also got hijacked; at DuckDuckGo, it did not.

This morning, as I was using Safari’s Web Inspector to see if I could get any more insight on the mechanics of the hijack (and take the screengrab you see above), another Twitter reply suggested that it could be an issue with CEA’s installation of WordPress. There is a history of exploits for that popular blogging platform that target incoming referrers from popular sites to send those clicks elsewhere; see, for instance, this Q&A thread.

(WordPress.com, this blog’s host, is a commercial service that runs WordPress; one of its selling points is having professionals stay on top of patches and security so I don’t have to.)

Sucuri LLC’s malware-checking site didn’t find any malware at CEA’s blog. But when I e-mailed somebody at the Arlington, Va., trade association, they did find a malicious script on the site that’s since been removed. And now, my original search takes me to the right page.

So I guess reporting this counts as this week’s good deed for the Internet… and maybe a start on next weekend’s USA Today column. But before I do that: Have you run into anything like this? Were you able to get it resolved? What else would you like to know about search hijacking?

Weekly output: blog hosts, QAM, Kojo Nnamdi, iPad rumors, Web chat

This week involved more real-time interaction with readers than usual.

2/12/2012: Tip: For a personal Web page, keep it simple, USA Today

First a reader e-mailed to ask about the easiest way to host a blog under a personal domain name; then, between my filing this piece and USAT posting it, two friends asked me the same question. I guess the timing was right for the topic. The column also offers a tip that emerged from a comment thread here: You can recharge an iPad over any random charger with a USB port, not just a higher-powered model labeled as iPad-compatible.

2/14/2012: Qualms Over QAM, CEA Digital Dialogue

Here I discuss the cable industry’s proposal to encrypt the local, public, educational and government channels that “QAM” (Quadrature Amplitude Modulation) tuners in digital TVs can receive without a box. Would you trade that–cable operators say encrypting QAM will free new customers from having to wait for the cable guy to show up–for the Federal Communications Commission making its “AllVid” proposal for box-free reception a standard for both cable and satellite? For further reading: The National Cable & Telecommunications Association’s Paul Rodriguez explains why cable operators don’t like the “traps” they now use to control access, while venture capitalist Fred Wilson argues for keeping clear QAM and providing the broadcast channels for free.

2/14/2012: Our Love/Hate Relationship with Email, The Kojo Nnamdi Show

I discussed ways to tame an overloaded inbox with WAMU host Kojo Nnamdi and two other guests, etiquette author Anna Post and IBM social-computing evangelist Luis Suarez. You hear more of me in the second half of the show, after Suarez’s call-in segment ended. (Tip: You can speak in paragraphs on public radio, but they have to be newspaper paragraphs.)

2/17/2012: The Only ‘iPad 3’ Story You Need To Read, Discovery News

The headline I wrote may oversell this story a bit–but, really, the feature set on the next iPad should not be that hard to figure out. And if this post isn’t the only next-iPad piece you elect to read, it’s certainly the only one I plan to write, just as I only wrote one next-iPhone post last year.

2/17/2012: Living a Connected Life (Web chat), CEA Digital Dialogue

My second monthly chat for CEA started a little slow, but I wound up getting enough questions from readers to stick around for an extra 15 minutes. One query I got confirmed my decision to devote next week’s CEA post to the upcoming reallocation of some spectrum from TV to wireless data mandated by this week’s payroll tax-cut bill. Another may yield an item for my USA Today column: how to connect an ’80s-vintage Nintendo NES (no, really) to an HDTV.