If you’ve been following along with the series thus far, then you’re likely seeing just how useful proper debugging can be especially when working on WordPress.
That is to say that not only are you able to gain valuable insights into your own projects, but you can see how WordPress core works, too.
At this point, though, we haven’t done much. As you may recall from the previous post (or if you haven’t watched the screencast, now is a good time to do so), you can see just how much debugging offers.
The truth is, we’ve barely scratched the surface. As I mentioned last time, this post and this screencast are going to focus specifically on the following:
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.
We’re still not at a point where we’re going to worry about changing variable values on-the-fly, but we’re definitely going to see how we can strategically use the debugger to step into certain functions, step over certain functions, and step out of certain functions.
Stepping Around Code
Before sharing the screencast, I want to define what it means to step around the code in a project. It sounds like something that we do whenever we’re navigating the codebase.
This is a bit of a lengthy post and I tried to make sure all of the explanations were made before viewing the screencast. After all, it’s much easier to read paragraphs of text about content and then seeing it play out in a short video rather than having a 15-minute video, isn’t it?
As useful as this can be, there’s still more to it. And that’s what we’ll review in the next post. Specifically, we’re going to look at how to inspect variable values, review what an array contains, and then how we can modify variables on the fly.
It’s powerful stuff, but make sure you’ve reviewed the first bit of content, carefully reviewed this post, and do a bit of practice before moving forward.