As some of you may have noticed, WordPress has, in its “wisdom,” introduced a new default editing system at its blogs, pretentiously called the “Gutenberg Block Editor.” It’s a flaming piece of shit which adds no value to the platform, subtracts (or hides) valuable functions that were present in the classic editor, is generally glitch-laden, and is extremely difficult to work with. This move is obviously in compliance with the Tech Axiom that if you can make a change to a platform, the change counts as an “improvement” no matter how miserable it makes the actual users of the platform, and how little they wanted it. (And yes, I have a Premium account, so I’m paying for this crap.)
I’m going to try to see if there’s a way to default the whole blog black to the classic editor, and if so, default it back. For now, however, I don’t know how to insert the very useful “Continue Reading” tag into posts, which means that any given post will take up an inordinate amount of space and crowd out the others.* I don’t have huge swatches of time to figure this out, so I’ll get to it whenever I can. Meanwhile, thanks, WordPress, for wasting my time, and fucking up my blog. You guys are the best.
I’d cancel them if I didn’t end up canceling myself in the bargain.
*I figured it out. What a pain in the ass.
WordPress sucks, yo. I’ve been looking into SubStack, lately, but it’s almost too much work to try and switch over…
LikeLiked by 1 person
I was happy with WordPress before this Gutenberg crap. Yeah, too much work to switch the blog over to another platform, but I’ve been looking for a place to post my writing, and both Medium and Substack are possibilities.
LikeLiked by 1 person
There are various ways to get around Gutenberg, but the most straightforward, if available to you, is probably to install and activate the (official, maintained by the WordPress dev team) “Classic Editor” plugin: https://wordpress.org/plugins/classic-editor/
LikeLiked by 3 people
I just came ere to post that.
LikeLiked by 1 person
Thanks!
LikeLike
I’m pretty sure it is available; I had read about that fix online. It’s just that when you’re pressed for time, and not-great about tech things, it’s irritating to have to spend the time to fix things that were fine before WordPress broke them. Will probably install that plug in this weekend, though.
LikeLike