I first wrote up Relevanssi back in 2015, when it saved my bacon on a client project. Last week it did the same thing again, and I remembered why I’d found it so cool in the first place.

From time to time, you’ll need to change the post type of one or more of your WordPress posts. One common need is to change a Post to a Page, when you realize a piece of previously published content is more “evergreen” than “blog.” You could create a new Page, cut-paste the Post’s content and title, and delete the Post—but doesn’t it make more sense to just change the one thing that’s the actual problem, which is the Post’s post type?

I have a client who needs to be able to create PDFs of his WordPress posts, including for custom post types that he specifies. I tried a few solutions, and WordPress PDF Templates is definitely the best I’ve found.

I recently found myself hunting for a solution that would allow a visitor to click a button to automatically download a free ebook. If you need to allow your users to download files from a WordPress site, today’s post will help.

One of the hardest things about debugging or extending WordPress plugins is often simply finding where a piece of code lives. A plugin may have many thousands of lines of code across dozens of PHP files, organized however the plugin developers thought made sense to them.

I installed Simple Lightbox on WPShout a few weeks ago, and it’s something I wish I’d done long before.

WordPress plugins can cause all kinds of errors: 500 internal server errors, PHP parse errors (also called syntax errors), errors that simply whitescreen your entire site, and more.

As a part of WordPress Security with Confidence, I built a feature that I felt a lot of people were hungry for. It’s a comparison table of WordPress security plugins. It starts to take people along the journey from “security is a serious topic that I have no idea how to handle” and toward “security is a set of problems I can solve in a variety of ways.” That transition is my motivation for the course, and it’s also the motivation for something I just made free: WPSecurityCompared.com. Which, well, makes it easy to compare WordPress security plugins.

A lot of people have written about how competitive WordPress has become and how difficult it is to make money with WordPress from products such as themes and plugins. Others believe there’s still plenty to be thankful for in WordPress.

So you’ve just installed an SSL certificate on your site, and you’re getting mixed content warnings? Noticing Google fonts not embedding, JavaScript files not loading, images missing, and so on? Welcome to another entry in an ongoing topic: why putting a WordPress site under SSL is harder than it should be, and what to do about it—mixed content warning edition.