
Phpinfo() shows me: VersionĒ.5.3 IDE Key webuilder. (I'm mimicking relevant parts of a remote netbeans xdebug config described here:ītw- I've gotten remote netbeans xdebug to work, I just like your IDE better). I then have to hit the blue stop button (turns gray) to continue working

webuilder&), and the step over, step into and step out buttons remain gray. The blue "Stop" debug square lights up, the entire script output (just a bunch of echo statements, every other one has a breakpoint) shows up in web browser window (.
Xdebug 3 idekey code#
Alternatively, you can set an environment variable so that you don't need to provide the -d parameters every time.I hit the green debug "Run" triangle, file code runs on remote sever, DOES NOT STOP AT ANY OF MY BREAK POINTS. These parameters have to be passed to the PHP interpreter using the -d command line parameter. Xdebug has various configuration options which we can use to let the PHP interpreter reach out to PhpStorm. Since we'll be starting the script from the command line, we will have to make sure it is started with the required settings to enable the debugger. Before launching the script, make sure that either a breakpoint is set or the Break at first line in PHP scripts option is enabled on the Debug page of the Settings dialog Control+Alt+S. This will ensure PhpStorm reacts when a debugging session is started and opens the debug tool window automatically. In PhpStorm, enable listening to incoming debug connections by either clicking ( in the classic UI) on the toolbar or selecting Run | Start Listening for PHP Debug Connections.

Listening for incoming debugger connections XDEBUG_CONFIG environment variable exists. Xdebug's remote_autostart (for Xdebug 2) or start_with_request (for Xdebug 3) option is enabled. Start a debugging session from the command lineīefore you start a debugging session with PhpStorm when running CLI scripts, make sure that any of the following requirements is met: This will also affect configurations that use the default project interpreter ( test frameworks', quality tools', and run/debug configurations) and commands run in the PhpStorm terminal. The selected interpreter will be set as the default project interpreter on the PHP page of the Settings dialog ( Control+Alt+S). In the popup menu that opens, select one of the configured local or remote PHP interpreters. If necessary, you can assign a keyboard shortcut for this action either directly in the suggestions list by pressing Alt+Enter, or at a later point as described in Keyboard shortcuts. In the suggestions list, select the Change PHP interpreter action. Press Control+Shift+A and start typing Change PHP interpreter. Switch between configured PHP interpreters on the fly The IDE will launch the script with the debugger enabled, and open the Debug tool window.īefore launching the debugger, make sure that either a breakpoint is set or the Break at first line in PHP scripts option is enabled on the Debug page of the Settings dialog Control+Alt+S. Alternatively, open the script in the editor, press Alt+Shift+F9, and select the script to be debugged. php from the context menu (make sure to pick the item marked with ). Right-click in the Project tool window, and select Debug |. We will need a Run/Debug configuration to start the debugger from within PhpStorm. A configuration can define additional arguments for the PHP interpreter as well as launch other commands prior to starting our script.

PhpStorm uses Run/Debug configurations to execute a script from within the IDE. To start debugging a PHP CLI script from within PhpStorm, perform the following steps. In the CLI Interpreters dialog that opens, the Configuration file read-only field shows the path to the active php.ini file.

On the PHP page that opens, click next to the CLI Interpreter field. In the Settings dialog ( Control+Alt+S), click PHP. Open the active php.ini file in the editor:
Xdebug 3 idekey update#
To avoid this problem, you need to update the corresponding sections in the php.ini file as described in Configure Xdebug and Configure Zend Debugger. These tools cannot be used simultaneously because they block each other. PhpStorm supports debugging with two most popular tools: Xdebug and Zend Debugger. We'll take a look at both options.īefore you start debugging, make sure that you have a debugging engine installed and configured properly. Alternatively, you can let PhpStorm listen for incoming debugger connections and start the script outside the IDE. You can start it from within PhpStorm and make it start the script and attach the debugger to it. There are several ways to start a PHP CLI debugging session. Various command line tools, daemons, message queue processing applications and other types of applications typically run in the PHP CLI. PHP applications are not always web applications.
