Author: Tom (Page 256 of 433)

Programmatically Add Multiple Post Terms in WordPress

September 16, 2014 / Tom / 0 Comments

A couple of weeks ago, I shared a simple gist for how to programmatically add post terms in WordPress. If you’ve read the series on importing CSV files into WordPress, then you’re likely to encounter something like the following scenario:

Given a CSV, apply multiple terms to a single post when the terms are delimited by another character.

So, for example, let’s say that you have a CSV and each value is, naturally, separated by a comma. Within one of the columns, words – or terms, in our case – are delimited by semicolons. Each value that precedes a semicolon represents a term (related to any given taxonomy in the system – this is irrelevant for this particular post).

Adding multiple terms to a post, or post type, is relatively simple and can be based off the functionality already shared.

WordPress and Small Team Source Control

September 15, 2014 / Tom / 0 Comments

Whenever I’m in the process of working on something for a client, my usual setup is something like this:

Work on the code on my local machine’s development environment
Keep the code in source control using GitHub
Use Dploy.io to deploy the latest commit to a staging server
Repeat until ready to launch

Straightforward enough, right?

But there have been a couple of times when I’m working with designers or front-end developers who need to work on, say, CSS files while I continue to do some of the backend work.

If they’re comfortable working with source control, then granting them access to the repository of the project and having them commit their changes to be part of the deployment process works fine.

But what about the case where the frontend developer is going to be working on various styles that you won’t personally be touching, and they aren’t using source control during the development phase of the project?

Easier Dev Practices For Everyone

September 13, 2014 / Tom

Comments are closed on this post. Rather than posting a comment, submit a few dev practices.

I don’t talk about this much on this particular blog because it’s outside the scope of the usual content on which I try to focus, but whenever there’s something worth mentioning, I bring it up.

As such, almost a year ago, I started Dev Practices. In fact, I have a very short post introducing the site on September 16th, 2013.

I still stand by what I said in the first post:

There are two absolutely amazing things that the Internet has brought us:

1. Animated GIFs

2. Memes

And when you combine the two together, you get some seriously good stuff, right?

When I set out to create the site, I didn’t really think of it as anything else that a dumb way to have some fun for a little while.

But it grew into a just a little bit more than that.

In fact, I’ve even considered porting it to WordPress and adding a lot of new features around it. Maybe eventually, but the honest truth is that it’s just a fun site, and there are so many other things that have priority.

So I’ve tried to compromise and improve just one part of the process. For now.
Continue reading

Importing CSV Files into WordPress: Clean Up

September 12, 2014 / Tom / 0 Comments

This is the final part in a series for how to Import CSV Files into WordPress.

Over the past few posts, I’ve walked through a strategy that I’ve found to useful and effective when importing large CSV files into WordPress.

Specifically, I’ve broken the approach down into three other articles each of which covers a high-level overview of how to achieve a certain part of the process through a mix of PHP, JavaScript, and pseudo-code.

Up to this point, I’ve covered:

How to setup the script to prevent timeouts
Working to build a back end that supports visual cues on the front end
How to display visual cues on the front use via Ajax

And the last part is by far the easiest: Clean up after yourself.

Importing CSV Files into WordPress: Visual Cues, Part 2

September 11, 2014 / Tom / 0 Comments

This is part three of a series for how to Import CSV Files into WordPress.

As mentioned in the previous post, one of the problems that comes with importing CSV files into WordPress – specifically large files – is giving the user feedback that something is happening while waiting for the process to complete.

But when your’e doing this within the context of a web application, it takes a little bit more work because everything happens in a single process. If you don’t show your users any feedback, then it looks as if the page is just sitting there.

Then again, because the process can take so long, you need to let the user know that something is happening.

Within the context of web applications, you can do that by using client-side JavaScript to essentially poll the server and ask for status updates.

Programmatically Add Multiple Post Terms in WordPress

WordPress and Small Team Source Control

Easier Dev Practices For Everyone

Importing CSV Files into WordPress: Clean Up

Importing CSV Files into WordPress: Visual Cues, Part 2

Current Projects