Tag: WordPress (Page 34 of 219)

Articles, tips, and resources for WordPress-based development.

When You Get Bored with WordPress, Part 2

October 25, 2018 / Tom

In Part 1, I wrote a bit about what happens when someone gets bored with WordPress development. Specifically, I raised points of interest in:

Is it the community?
Is it the social (perhaps read: political) aspects of it?
Is it the fatigue of learning something new?
Is it the notion that you’ve learned all there is to learn about it?
And more.

And though I think it’s completely reasonable and acceptable to say “I’m ready for something new,” I think doing so under the guise of “I’ve learned all there is to learn about WordPress” to be a bit of an overstatement.

It’s a big piece of software with a lot of APIs, tools, and libraries around it. To make the claim that you’ve learned everything, there is to know about WordPress may be a stretch. I’m not saying it can’t be done (because there are people who have been involved with the project since it’s initial fork), but it seems unlikely.

Regardless, I thought I’d spend a few more words talking about the areas in which I’ve been involved and why I moved away from them as well as why I moved into the areas I’m in now.

WordPress Database Merging Made Easy with WPMerge

October 18, 2018 / Tom

This is a sponsored post from the fine team over at WPMerge. The following tutorial provides all you need to know to get started.

Whenever we’re working with WordPress environments, it’s common for us to clone the production database to our local development database but not necessarily the other way around.

For example, let’s say that we do work in the local development database that contains new posts, perhaps new WooCommerce orders, or other data that you’d like to share with the production site.

At this point, you have two versions of the database that you’d like to merge without losing changes in either environment.

To manage this, we have a few choices:

You can note all changes made in the local development site and meticulously perform them on the production site.
You can copy changed rows from the development site and run the queries on the production site. The problem with this is when the new data comes in; users may have the same IDs used in the local development database ultimately creating a conflict.
With currently available tools, you can move the development database to the live site. But you’d lose the vital changes like comments or orders that happened on the live site during development.

None of them make for an ideal deployment workflow.

An Alternative to the WordPress template_redirect Hook

October 17, 2018 / Tom

The majority of the work that I do right now focuses on custom plugins or utilities that work on top of WordPress.

If you were to conceptualize how many of the projects that I build are put together, you’d review WordPress (and all that it entails) as the foundation, and then the code has having a layer that communicates with WordPress, and that may communicate with third-party APIs.

When doing this, though, there’s often a front-end component that requires I render information into templates. Though building templates for WordPress aren’t inherently difficult (though I do wish we had a bit more than template tags – such as a templating engine, that’s another post), I think it’s worth looking at a couple of ways that we can handle custom templates that we bundled with plugins.

One of the first questions that’s often raised with this statement, though, is

Why would you include custom templates in a plugin?

And I get it on some levels.

Keeping templates in a plugin blurs the lines a bit between themes and plugins especially when you leave themes for presentation and plugins for business logic,
Asking users to copy theme files on from one location to another is bad user experience.

But there are a few rebuttles or perhaps outright exceptions to the above cases.

Using Kanban in WordPress Development

October 16, 2018 / Tom

Periodically, others will ask how I manage to organize the various tasks, assets, resources, and related things throughout a project. First, I’ve decided to keep Pressware small (and this is for some reasons), so it allows me to run it differently than if it were, of course, larger.

Using Kanban in WordPress Development: A Basic Example

Secondly, I typically use a very scaled down version of a kanban board. For those who aren’t familiar, kanban is defined like this:

a Japanese manufacturing system in which the supply of components is regulated through the use of an instruction card sent along the production line.

To that end, I thought I’d share a brief overview of how I typically setup each column and each card as well as the tools I use to handle each task.

Quick Tip: Sanitize Post Data in WordPress

October 11, 2018 / Tom

The more I begin to try to use PSR-2 coding standards and tools such as GrumPHP (and those related to it), the more I find that the quality of the code I write can be significantly improved in minor ways.

PHP Coding Standards with Code: PSR-2

And I don’t mean to sound contradictory: I mean, the idea of having something “significantly” improved in a “minor” way doesn’t exactly jive, does it?

But hear me out.

Imagine that you’re able to write clean, readable, maintainable code using coding standards that are not only modern, but built into PHP, play nicely with WordPress, and that is more readable than some of the other ways we may have done it in the past or when using other tools for coding standards.

Wouldn’t you be interested?