Debugging WordPress PHP with VS Code and MAMP

This is the blog post I wish existed a few weeks ago when I started trying to configure Visual Studio Code to debug PHP and WordPress interactively. Although this setup might not work for everyone depending on your environment, it will save anyone using MAMP already a hell of a lot of time.

The Benefits of Debugging WordPress

One of the reasons I use VS Code is because of its capabilities as an interactive debugger, but how is that different from other types of ‘debugging’?

For a lot of things in development, we can get away with having the program print out some information as it is executing, think console.log for JS or echo, var_dump for PHP, and so on.

But as things get more complicated, you might need to get a better look at what is going on underneath the hood. Enter interactive debugging, which allows you to inspect different variables as the program is executing and step through functions and control flow structures until we decide to release certain breakpoints.

debugging wordpress code in vs code

Typically, this helps you resolve issues a lot quicker, especially when something isn’t solved easily by printing out a few key variables.

Enable PHP Debugging in VS Code

VS Code came with support for NodeJS debugging out of the box, so I expected things to be as straightforward for PHP, since it’s more widely used.

Sadly, it was not so.

First, you need to install the PHP Debug extension for VS Code by either running the following command in the command palette or searching for the package in the extensions menu:

ext install php-debug

From here is where things got murky for me. If you install the debugger package, and try to run the debugger it will start throwing errors. Reading the docs for the extension, it says it needs something called Xdebug.

After reading the links to Xdebug on the docs, I embarked on a long trek to download and compile Xdebug from source, configure it with the version of PHP installed on my system (php7), and then it proceeded to keep failing when I tried to have the PHP thread talk back to the debugger.

As it turns out, since I was using MAMP as a local server, Xdebug already comes installed with MAMP, so all you really need to do is instruct MAMP to use Xdebug for the current version of PHP.

I’m sure the other stuff would have been the necessary path if I was using the command line to manage the Apache/MySQL servers.

Enabling Xdebug for MAMP

After spending hours compiling binaries and exporting PATHs, the fix was almost embarrassingly easy. To enable Xdebug on MAMP, we just need to add a few lines to the two php.ini files MAMP references.

Open up the following files in a text editor:


Make sure to look in MAMP to see what version of PHP is set as the default, since there are likely dozens of PHP folders inside of the application.

With the files open, add the following lines at the bottom of each file:


At that point, you should be able to restart MAMP, throw a breakpoint in Visual Studio, then hit that breakpoint from your web browser on localhost:8888 or whatever your MAMP config specifies.

Credit to Sean Patterson for the MAMP config details. Hopefully, this will help out some other poor soul by adding to the Google keywords that might lead you to salvation.

8 thoughts on “Debugging WordPress PHP with VS Code and MAMP”

  1. Thanks for the link share and that things are working in Visual Studio Code now too! I’ll have to check that out on my next project.

    1. BrownBearWhatDoYouSee says:

      Thanks for documenting the path forward w/ MAMP! It saved me a ton of time. VS CODE is worth a look if you haven’t already. Thanks for stopping by 🙂

  2. Bob Hardy says:

    Thanks for this helpful post. I struggled in the same ways you describe before reading this. It is what you say – embrassingly easy to get this going using MAMP.

    1. BrownBearWhatDoYouSee says:

      I’m glad this worked for you and I could save someone some pain 🙂 Thanks for reading.

  3. SC says:

    One small change. The date stamp (20100525) was different on my computer. Thankfully the correct one was in the php.ini file but I could have found it by following the file path. Here was mine:


    1. BrownBearWhatDoYouSee says:

      Thanks for posting about the differences! Maybe this will help someone else out if their’s is different as well.

      Thanks for reading,

Leave a Reply

Your email address will not be published. Required fields are marked *