By now, we’ve covered a lot of ground as it relates to working with WordPress and debugging. And this is especially true as it relates to working with tools and plugins available within WordPress. If you’re just joining this particular series, please make sure you’re caught up with the following posts:
- Reading and Understanding WordPress Error Logs, Part 1
- Reading and Understanding WordPress Error Logs, Part 2
- Basic Debugging Within WordPress
In the previous post, recall that I said the following:
But if you’re looking to get into the world of professional, practical debugging from within your IDE, then it’s important to understand the what, how, and why.
And we’re finally ready to look at what this requires. To get started, however, means that we need to understand a few things about Xdebug, the terminology, and to have an IDE that’s consistent for everyone reading this particular series.
So this is going to be broken into two parts.
- First, we’re going to look at the terminology required for debugging and make sure that we have a proper IDE setup in our development environment,
- Next, we’re going to look at how to ensure we’ve properly installed Xdebug and then wiring it up to our development environment so we can put it to work.
If you’ve read a variety of content throughout this blog over the past few years, some of this may seem familiar. If not, no big deal. Remember the goal is make sure we’re all on the same level as we proceed forward with the work mentioned above and throughout the rest of the series.
With that said, let’s get started.
Installing Xdebug, Part 1
As mentioned above, this set of posts is going to serve one of two purposes both of which can be succinctly described (the second of which will be described in the next post):
- Debugging Terminology
- Installing an IDE
Though many reading this will already be familiar with some of the terminology (especially if you’ve used client-side tools or even server-side tools before), and you already have an editor of choice, it’s important to make sure that we are at least working with a consistent foundation.
Configuring Your IDE
In the next post, we’re going to look at tying Xdebug into our IDE. Assuming that you’ve followed the steps in this post and that all has gone well, you should be good to go as it relates to preparing to debug WordPress projects.
Until we have it running within an IDE, though, it’s not as useful (or it’s more difficult than it has to be). So next week, we’ll look at exactly how to do that.