WordPress and PHP

I got a bill from 1&1 / IONOS last week for PHP 5.6 Extended Support. I was a little surprised by this, since I thought I’d already taken care of updating PHP to a supported version, but it turns out that I was remembering updating from 5.4 to 5.6 three years ago. (Tempus fugit.) It looks like 5.6 reached EOL at the end of 2018. So I guess I’m paying $7 now for not having upgraded PHP in a while. I went ahead and updated to 7.2.15, so I should be good now for a while, though I guess I should update to 7.3 at some point. And I’ve got WordPress updated to 5.1.1 too. Everything still seems to be working, which is nice.

Every once in a while, I think about switching to some kind of managed WordPress install, so I don’t have to worry about this stuff anymore. Maybe just the $5/month plan from wordpress.com or something like that. But I still like futzing with this stuff a little, so for now, I’ll stay with the traditional web hosting plan, where I’m free to mess things up and forget to update PHP and stuff like that. But I think I’m getting close to the point where I’m going to want to hand this stuff off to somebody else and just concentrate on the blogging and not worry about the sysadmin side of things. Maybe in another three years.

WordPress 5

I just updated this blog to WordPress 5.0.3. I’d been putting off updating it to WP 5, partially because I wanted to wait until they’d gotten a few point releases out and fixed any major bugs. And partially because the big new feature in WP 5, the Gutenberg editor, is not that interesting to me. I tried it out on my test site, and didn’t really like it. For now, I’m leaving the Classic Editor plugin installed and enabled. I’m glad they’ve provided this plugin, rather than trying to force the new editor on people. I’ll probably give Gutenberg a try again at some point, maybe after watching a video tutorial or two. (I haven’t gone looking for any, but I assume they’re out there.)

There’s been a lot of controversy and grumbling about Gutenberg, but I don’t have a problem with it, as long as they’re not forcing it on people, and as long as they take constructive feedback on it and keep working on it. I’m just thankful that WordPress continues to exist as an open source project, and continues to get updated. I’ve been using WordPress for almost five years now, and it’s been great.

broken links

I installed the Broken Link Checker plugin on my site today, and spent probably too much time fixing broken links. Doing blog maintenance like this feels like productive work, but really isn’t. But it’s kind of fun, and lets me stroll down memory lane a bit, rediscovering stuff like Get Your War On, which I’d forgotten about.

A lot of dead links can be easily replaced with ones from the Wayback Machine, and the plugin helps with that. But some of the links on this blog seem to have completely disappeared from the internet, which makes me a little sad. Nothing lasts forever, I guess, even an interesting review of The Two Towers from a newspaper in Las Vegas that apparently only existed from 2003 to 2005. Oh well.

I’ve been linking to Wikipedia, the NY Times, and Amazon a lot lately. I think (and hope) that those sources will be around for a while, and that they won’t mess with their URL schemes in a way that breaks old links. (For the most part, they haven’t, at least recently.)

The plugin has found more than 600 broken links so far, and I’m not even sure if it’s done crawling the site yet. I need to be careful about getting too wrapped up in this, or I’ll be doing it all day. (Or maybe all week.) I’ve actually talked myself into deleting some old posts, where the links are dead, and I didn’t really say anything interesting about them. That’s always been hard for me to do, but I’ve got more than 2000 posts on this blog, so it makes sense to cull some useless ones out occasionally.

TidBITS redesign

I’ve been reading the TidBITS newsletter for years. They’ve been publishing it for 28 years; I’ve been subscribing to it for more than ten. (I’m not sure how long exactly, but at least since 2002.) They just unveiled a new design and back-end after many years under the old design and system. The new system is based on WordPress, which isn’t surprising. Lots of websites (including mine) are running on WordPress these days. The design looks good. I haven’t seen any hiccups with the back-end yet, so hopefully they’ve done a good job with that. TidBITS has always been a good source of Apple news and analysis, better in general than most of the more modern web sites. (I won’t mention specific sites, but I’m thinking of certain sites with a lot of “top ten” listicles, sponsored content, and more space devoted to ads than articles.)

I’m always interested in how sites like TidBITS remain commercially viable. I doubt they make much money from ads these days. They probably get a modest amount of money from their membership program. And they have something called the TidBITS Content Network now too, which is interesting. They used to run Take Control Books also, but they sold that off a while back. I should probably pay them for a one-year membership. I keep meaning to do that, but I never quite get around to it.

I like the newsletter model for this kind of content, and I wish more people would use it. I’d love to find a Windows newsletter that’s as good as TidBITS. Years ago, I used to subscribe to Windows Secrets and that was pretty good for a while. It looks like they’re still around, but as a paid newsletter only, and it appears that none of the original contributors to the site are still involved. I found a recent post on Woody Leonhard’s site that runs through a little of the history of Windows Secrets. It used to have a lot of good content, from people like Woody, and Brian Livingston, and a couple of other good tech writers whose names I can’t remember now.

New SSL certificate

This blog should now have a new, slightly less fancy, SSL certificate. I had been using a $49/year certificate from 1&1, my hosting provider. It was issued via GeoTrust, and worked fine. A while back, 1&1 switched me to a slightly more expensive plan that included a free SSL cert. But of course they didn’t automatically move the paid one over. And there wasn’t an obvious way to do it from the control panel. I meant to call them about it, and didn’t get around to it before the cert renewed in June. So I had planned on doing that at some point next year before it renewed again. But I got an email this week telling me that it would renew this month. I do have an invoice from them saying that I renewed it through June 2018, so I’m not sure why they think it’s expiring now. But that finally motivated me to call them and get the cert moved over to the free one. The call was pretty simple and easy: only a short hold time, and the rep I got spoke English well, fixed things quickly, and didn’t try to sell me on any new services. Looking at the cert in Firefox now, It looks like a perfectly good DigiCert certificate, good through December 2018. Now let’s see if they really canceled the old one, or if they try to bill me for the renewal next month.

1&1 hosting plans

I’ve been using 1&1 for web hosting for a very long time. Their reputation is mixed, but I’ve never had any huge problem with them. An occasional hiccup, but not that often really. I’m currently paying about $6.25 per month for my hosting plan. But I just got an email saying that they’re changing me over to their “1&1 Unlimited Plus” plan, which will cost me $11 per month. This supposedly includes an 8% discount off their normal rate, which I guess would make the normal rate $12.

Looking at their web site, it looks like new customers can get Unlimited Plus for $5/month for the first year, and $10/month after that. So I’m a little confused about how $11/month is a discounted rate. Maybe I’ll e-mail them about that. At any rate, it looks like the new plan might include a free SSL certificate, which I’m currently paying $50/year for, so that would offset the price increase. (Of course, there are other ways of getting free SSL certificates these days, so I shouldn’t have to pay for SSL regardless.)

I don’t really have any intention to move off 1&1, but a price increase is always a motive to look around at alternatives.

WordPress syntax highlighting

I occasionally post code here, and I’ve never been entirely satisfied with the various ways that one can post nicely-formatted code on a blog. This blog has been around for so long that I’ve gone through several approaches. Recently, I’ve been putting all my code snippets in Github Gists, and then embedding those Gists here.

That looks pretty good, and works pretty well, but I’ve discovered a couple of downsides to that method. First, the code itself is not actually in my posts, so it doesn’t show up in searches, either here at the blog or (presumably) in Google or other search engines. I realized this a while back when I tried to search for a past post, using a bit of code that I knew was in the post. When I didn’t find it, I realized that of course the code wasn’t in the post, it was only out on Github. So I wanted to fix that, and get the code itself into my post database.

Second, the company I work for has started blocking the Gist site. I’m not sure why, but I guess maybe it’s occasionally used to post malicious code? Regardless, it’s a problem, since I sometimes want to bring up an old post of mine at work to remind myself of how I solved a problem in the past. When I do that now, the post is visible but the embedded gist is missing. And if my company is blocking gists, other companies are probably doing it too, so other people looking at my blog might be confused when they see a post with missing code.

So there are some good reasons to include actual code in my posts, rather than relying on Github. I could go back to just wrapping the code in <pre> and/or <code> tags, but I wanted to have something that would look at least as good as the embedded gists. So I started looking at syntax-highlighting plugins for WordPress.

I looked at Enlighter and WP-Syntax. Enlighter looks pretty cool, but I decided to go with WP-Syntax in the end. It uses GeSHI, which I’ve used before (in Drupal), and supports a lot of languages, including X++, which is a pretty obscure language. I installed it about a week ago. Today, I decided to spend a little time editing some of my old posts to move code from gists to WP-Syntax. It worked out pretty well. (And I’m still linking to the gists, so if the code gets scrambled, it’ll still be there on Github.)

To some extent, I guess this is just pointless busywork. My old posts don’t really get a lot of hits, and I really don’t refer back to them that often. But it was a nice little way to spend an hour on a cold Sunday afternoon, and it gave me a sense of accomplishment.

Amazon Affiliate Links

Amazon has recently made some changes to their affiliate program that are going to have a negative impact on some bloggers. Here are a couple of articles about the change, from The Verge and The Digital Reader.

I’ve been using Amazon affiliate links here on my blog for a long time. And I’ve never earned a penny from them. And that’s fine. I used to use SiteStripe to generate fancy image links, but I’ve had problems with those since I switched from Blogger to WordPress. So lately I’ve just been using SiteStripe’s short URL links. For me, it’s really just a way to get a short URL that might (but probably won’t) make me a buck or two at some point. But there are some sites that have based their “business model” on Amazon affiliate links, and they’re going to be in a bit of trouble. The Wirecutter and The Sweethome used to be in that category, but since they’ve been acquired by the NY Times, maybe they don’t have to rely so much on Amazon.

Either way, relying on something as fragile as affiliate links for anything other than a little extra coffee money has always seemed a bit daft to me. On the other hand, online advertising is a mess too, with so many people using ad blockers, and getting people to pay for content doesn’t usually work out too well either. I’m glad I have a good day job!

WordPress post formats

In addition to doing my taxes today, I also spent some time messing around with this blog. The theme I’m using, Stargazer, supports post formats. I’ve messed around with them a little, marking some posts as video, audio, quotes, and images. I thought the feature was kind of nifty, though it didn’t seem to have that much utility.

Over time, though, I’ve started to see some downsides to post formats. There seemed to be some issues with the way they were treated in certain plugins. (Specifically, it looked like they were being ignored, and the plugin would only see standard format posts.) So I thought it might be a good idea to just reset all the posts to “standard,” and avoid using them in the future.

I couldn’t initially find a way to get a list of posts by format. I did some searching and found the Post Format Filter plugin. It hasn’t been updated in a long time, but it still works, so I used that to search out and reset all my posts to standard. That was kind of boring work, but it allowed me to stumble across some fun old posts.