We’ll need to define a new interpreter, so click the button next to the Interpreter: drop down, to be taken to the Interpreters management screen.
The settings we want are found in the Preferences pane under Languages & Frameworks then PHP (if you are as lazy as I am, you can use CMD/CTRL+SHIFT+A to search actions and then type ` interp` to go right there). Doing this straight away tends to make potential problems less likely to appear further down the line.
Phpstorm debugger not installed install#
Is it using Apache? Is it using Nginx and PHP-FPM? Who knows! It’s really not that important, but generally, the first thing I do once I’ve opened the project is to tell PhpStorm which PHP install I’m going to use. It’s important to consider these factors when you are deciding what to make your projects root to make mapping paths easier - more on this later.Īt this point, I have no idea how this vagrant box is configured. I’d cloned VVV into the `This gave me a project open that linked directly to the webroot of the `` URL. The first thing I did was to open the project in PhpStorm. The good news is this was really simple and allowed me to hit the current stable version URL at `` quickly and easily to see my working WordPress install. For this exercise, I installed the plugins that the documentation recommended, and then cloned the repository, and used `vagrant up` to bring the box up and run its provisioners. It has various versions of WordPress running under separate URLs.
Varying Vagrant Vagrants is a Vagrant setup designed to make working with WordPress as easy as possible. So I decided to blog about not only how to get debugging working, but the process I used to figure out exactly what needed to be changed. Recently we’ve made a lot of changes to debugging in PhpStorm to try and make the process as simple as possible. Who do i know that uses PHPstorm with VVV and XDebug? I need some guidance on getting things setup.
0 kommentar(er)
