At the very end of july, I shared all of the details about my upcoming “Improve Your WordPress Development Skills” course. Feel free to read the details in their entirety; however, note that this is the week of course!
Author: Tom (Page 314 of 427)
In three previous posts, I’ve mentioned that I’ve been slowly refocusing my own business to focus solely on working with WordPress. This particular focus includes:
- Renaming the company
- Doing a long, hard search for a support system that I like
- Trying to find balance with the WordPress Plugins Repository
- And even beginning to offer some online courses
In order to keep this momentum, albeit it very slow momentum, going, I’m looking to begin experimenting with self-hosting WordPress plugins. Specifically, I’m going to be using Auto Hosted.
And much like I did with support systems, I’m going to be evaluating it by actually, you know, using it.
But here’s the thing: I need your help.
Yesterday evening, I had to take some time to migrate my site to a new server because I had outgrown the service on which I started.
While doing so, I realized I’ve never bothered to share my WordPress site migration process.
Honestly, there’s nothing particularly unique about it. Furthermore, when it comes to deploying things to staging, I’ll often use tools that interface with my GitHub account to push out the differentials.
Migrations. Not quite what we had in mind.
But when it comes to move a single site installation from one server to another, I typically follow the same process.
Generally speaking, the majority of the work that I do with third party APIs is done so in the context of WordPress, but the truth is that what I’m about to say is subject to whatever platform you’re work with – be it .NET, Rails, COBOL, or whatever you or your dad maybe using :).
But a feature in Standard recently quit working because of an underlying change in a third party API. Now, to our credit, we normally do a good job with following blogs and release notes when an API is going to change.
In this case, there was no documentation on any of this – something just stopped working, so we needed to dig in and fix it. The fix is under testing and will be released later, but the point that I’m trying to make is that there is always a danger in working with third party APIs.
In the previous post, I spoke briefly about WordPress directories. Specifically, I talked about placing files in an `inc` directory whenever building a theme. This lead to a comment by Richard that I thought was worth covering here:
In the theme folder, sometimes I see people use “lib” to include theme assets and other times I see them use “inc”, as you’ve done here. Is there a reason for one vs the other?
I gave a short response in the comments, but thought that this warranted a longer form explanation to share my perspective, and to hear what you guys have to say, as well.
Kinsta offers premium managed WordPress hosting for everyone, small or large. Powered by Google Platform and strengthened by Cloudflare, they take performance to the next level. All hosting plans include 24/7/365 support from their team of WordPress engineers. Get started with a free migration today.
If you are looking for WordPress guides and unbiased reviews, I recommend checking out WPKube. They also have an exclusive deals section.