Before you start debugging, make sure that you have a debugging engine installed and configured properly. PhpStorm supports debugging with two most popular tools:
XDebug
and Zend Debugger
.
These tools cannot be used simultaneously because they block each other. To avoid this problem, you need to update the corresponding sections in the php.ini
file. To find out which php.ini file is active, create and run a test file with phpinfo(),
then search for the Loaded Configuration File.
For more information on configuring debugging engines, see Configuring XDebug, Configuring Zend Debugger,
http://confluence.jetbrains.com/display/PhpStorm/Xdebug+Installation+Guide
, and http://confluence.jetbrains.com/display/PhpStorm/Zend+Debugger+Installation+Guide
.
With PhpStorm, a PHP debugging session can be initiated either through a debug configuration or without it. The latter approach is also called Zero-configuration debugging. PhpStorm supports three main ways to initiate a PHP debugging session:
No matter which method you choose, you can specify the scripts requests to which you want PhpStorm to ignore during debugging. This approach can be useful, when your application contains scripts that use AJAX. Suppose you have a menu-ajax-script.php that "reloads" a part of your web page. This script works properly so you do not need to debug it. However, this script is still requested during the debugging session. To have incoming connections to this script ignored, add the menu-ajax-script.php script to the skipped paths list. You can also group such scripts into folders and add these folders to the "ignore list".
When using Xdebug, you can also debug PHP applications in the multiuser mode via Xdebug proxy servers.
In this part: