After you’ve worked with WordPress for any extended amount of time, it’s likely that you’ve worked with post metadata in some capacity. Perhaps you’ve simply read metadata from the database, or maybe you’ve both written to and read from the database table, as well.
It can be a really powerful API whenever you need to associate certain information with your posts (or, if you’re into abstracting things even more, to your models).
That said, what happens when you want to include information from the metadata table but don’t have the convenience of plugins such as SearchWP or Relevanssi?
Furthermore, assume the use case is just for administrators and it’s only for the administration area of WordPress. That is, you want to search your posts from within the All Posts screen but you want to include the post metadata in the search criteria, as well.
Over the past few years, I’ve spent a significant amount of time writing about a lot of things on how to achieve certain things in WordPress. And I don’t regret it (after all, it’s my career and it’s even the subtitle and focus of this blog).
But one of the things that I’ve opted to neglect is a focus more on topics that interest me such as object-oriented analysis, programming, design, and implementation. (And, of course, doing so within the context of WordPress.)
And sure, there are some articles where I’ve touched on it but I recently took a week off of pretty much everything except my [growing] family and during that time, I took stock of a variety of things.
One of those things included this particular site, its content, and the general focus of my career.
A few months ago, I had the pleasure of writing the forward to Cal Evans book Using the WordPress REST API. Shortly thereafter, Cal asked if I’d join him on his podcast, Voices of the elePHPant, to talk a bit about software development in the context of WordPress.
And given that that’s what I’ve spent the majority of my career doing, it made sense to participate.
This not only gave me a chance to catch up with Cal “face-to-face” but also to share a bit about what it’s like working in this particular corner of the PHP community and in the WordPress economy.
Last month, I spent time thinking about why I’d want to do so versus just letting them sit. Though there are multiple reasons for doing so, there’s one reason to which I kept returning (and plenty of others I’ll outline in moment).
But first, the TL;DR is this: There’s a single side project I want to work on without any distractions.
That’s it. Nothing elaborate, fancy, or groundbreaking. The thing about having a variety of other repositories available, though, is that there are occasional emails about bugs, feature requests, etc., all of which are appreciated but most of which I don’t have time on which to focus at the moment.
Instead, I think my time can be better spent on other work. And I think I want to spend my time on other things.
But one problem that comes with using these as my main DNS servers (and maybe others, I don’t know as I’ve not tried them) is that when I’m using cURL to make requests to a third-party server, it will often result in an a 404.