Author: Tom (Page 319 of 432)

Beta Testing Self-Hosted WordPress Plugins

August 19, 2013 / Tom / 0 Comments

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.

My WordPress Site Migration Process

August 16, 2013 / Tom / 0 Comments

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.

The Danger of Third Party APIs

August 15, 2013 / Tom / 0 Comments

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.

WordPress Directories: inc and lib

August 14, 2013 / Tom / 0 Comments

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.

The WordPress Theme Customizer: Adding a New Setting To An Existing Section

August 13, 2013 / Tom / 0 Comments

Since the release of the WordPress Theme Customizer, my team and I have been more and more interested in using it as a way for users to make changes to the appearance of their theme without the use of the dashboard.

As powerful as the dashboard is, the “Appearance” section creates a disconnect between what the user toggles (or selects, or inputs, etc), and what they see on the front end.

The Theme Customizer mitigates that issue.

The thing is, there are a few nuances that come with implementing it in your theme. Though I’m not trying to cover everything here, the point of this post is show how you can introduce a new setting into an existing section.

Beta Testing Self-Hosted WordPress Plugins

My WordPress Site Migration Process

The Danger of Third Party APIs

WordPress Directories: inc and lib

The WordPress Theme Customizer: Adding a New Setting To An Existing Section

Current Projects