Recently, I’ve started volunteering to give more talks to local user groups and conferences. Normally, I have some kind of slide deck to go along with those as a resource. To keep all of these in one place, I’ve created a Talks page as a kind of repo for the talks I’ve given or talks in development.
Recently, we wanted to create a Slack group for a meetup group in our city. We also wanted to auto-send Slack invites to folks so the admins didn’t have to.
Everyone (especially devs!) love Slack, and we’re on it all the time. One of the best ways we can keep in touch outside of the meetup (meetup.com doesn’t really have a good interface for chatting with group members in between meetups) is to make sure we’re able to communicate and ask questions here between meetups.
They say if you want to learn something, teach.
Or scratch your own itch.
Or just do it.
In any case, I had an itch that I have been wanting to find a fix for for a while.
If you are a developer like me, you began figuring this “WordPress thing” out through tutorials, trial and (mostly) error, and trying a lot of different things out.
Also, if you’re like me, you got into this for several reasons, one of which is the joy of helping people out and getting them a website setup and launched. I love the satisfaction of getting that project launched and the joy these folks have when they realize they can manage their own publishing.
And of course, if you’re a developer like me, you have a shared hosting account with at least a dozen different websites that are small personal projects or folks on the “friends and family plan” (read “free hosting” 🙂 ). This means I have a dozen or so sites I want to make sure I keep updated, but don’t want to spend a lot of time updating.
So, I decided to learn enough bash to write a script that would execute WP-CLI commands on my local environment as well as my shared hosting.
Here’s how I did it…
Recently, I was asked to add a button to the visual editor for posts and pages on a WordPress install that would insert the
<!--nextpage--> code for article pagination . I had done this before, but wanted to write about it here, since I’d totally forgotten how to do it, and wanted to make sure I had a snippet or two for reference.
My friend and I are working on a little side project. It’s a job posting site for an industry we’re familiar with: ESL jobs around the world. While this project could be seen as “just another job board”, we’re hoping to add some features that will make it fun to use and valuable for schools and recruiters. I of course want to build it on WordPress, but to get a some of the functionality I want, I need to expose some post meta to the WP REST API.
In researching how to do this, I quickly found out that the WP REST API doesn’t naturally expose post or user meta. As with most things WP REST API, you don’t have to go too far down the rabbit hole before you find a practical article written by the Josh Pollock. While the
register_api_field function isn’t in use anymore, the
register_rest_field function is, so this article and that function were all I needed to get going.