In the most recent post in this series, I walked through the process of integrating Xdebug with your IDE. And given that I’ve been using Visual Studio Code as my IDE of choice, that’s also the IDE I’m using as the example.
Furthermore, it’s cross-platform, easy enough to get started for beginners, but powerful enough to extend and operate for more experienced programmers (and for the rest of us who fall in between).
In the last post, I stated that I’d be doing a series of screencasts. Specifically, I wrote the following:
Starting in the next post, I’ll begin sharing some screencasts that walk through how to debug functions and variables, change values on the fly, work with the debug console, and more.
In this post, I’m going to have a short screencast providing an introduction to debugging WordPress the first part of this series. Namely, launching an instance of a site built using WordPress and using the basics of debugging a plugin.
An Introduction to Debugging
Because this screencast is the first in a series and because I don’t want to assume a person has previous experience, I’m going to start at the most basic level.
In the next post, we’re going to look at more advanced things we can do such as stepping into functions, stepping out of functions, and stepping over functions.
After that, we’ll turn our attention to more advanced things such as watching variables throughout the lifetime of execution of a plugin and then how to change variables during execution.
For now, though, why not take some time to practice and set a breakpoint in a few different plugins are a few different areas of code in a WordPress-specific application?