PHPStorm + XDebug Setup Walkthrough

by

I’ve found a more modern and easier solution partially based on CrasyCoder’s post.
The steps you need to do are the following:

  1. If your brand new php installation doesn’t contain php.ini, rename the php.ini-development to php.ini
  2. Install xdebug with help of the wizard: http://xdebug.org/wizard.php Follow its recommendations literally.
  3. Put in your php.ini the string: xdebug.remote_enable=1
  4. Go to PhpStorm’s settings: settings->php. Select or reselect directory containing php. Make sure you see ‘Debugger: Xdebug x.x.x’ string (where x.x.x stands for installed version)
  5. Install an extension for your favorite browser from here: http://xdebug.org/docs/remote
  6. From the main menu (not the settings window) go to ‘Run->Edit configurations’ and add new ‘PHP Built-in Web Server’ configuration. Point the ‘Document root’ to your project’s directory. Note the port number.
  7. Chrome browser: enable the extension pressing on the little bug in the rightmost side of the omnibox and selecting the Debug option. Other browsers’ extensions should work similarly.
  8. In PhpStorm’s menu enable the ‘Run -> Start Listen for PHP Debug connections’ option.
  9. Set a breakpoint in your code in PhpStorm.
  10. Run (not debug) the configuration you created in step 6.
  11. In your browser go to localhost:port where ‘port’ is the port from step 6. Your PhpStorm should stop on the breakpoint and you can start squashing bugs in your code.

Considering that:

Steps 1-5 are made once per php installation.
Step 6 is made once per PhpStorm project.
Steps 7-8 are made once per debuggin session.
Steps 9-11 are made each program run.

More Related Contents:

  1. enabling xdebug remote debug makes apache server very slow
  2. How do you debug PHP scripts? [closed]
  3. XDebug and RESTful server using PHPStorm or POSTman
  4. Xdebug PhpStorm don’t stop breakpoint
  5. How to setup Docker + PhpStorm + xdebug on Ubuntu 16.04
  6. Phpstorm doesn’t know how to run WordPress
  7. Solution for “Fatal error: Maximum function nesting level of ‘100’ reached, aborting!” in PHP
  8. Increasing nesting function calls limit
  9. Eloquent ORM Code Hinting in PhpStorm
  10. netbeans shows “Waiting For Connection (netbeans-xdebug)”
  11. How to get xdebug var_dump to show full object/array
  12. Difference between WebStorm and PHPStorm
  13. Can IntelliJ IDEA encapsulate all of the functionality of WebStorm and PHPStorm through plugins? [closed]
  14. PHPStorm – Run Filewatcher on existing files?
  15. Will enabling XDebug on a production server make PHP slower?
  16. PHP on Windows with XAMPP running 100 times too slow
  17. Is it possible to get Ruby syntax highlighting in PHPStorm?
  18. mysqli + xdebug breakpoint after closing statement result in many warnings
  19. PhpStorm – Advantages of Editing Deployed Files Directly vs Downloading and Syncing
  20. How to disable parameter name hints in PhpStorm?
  21. How to document magic (_call and _callStatic) methods for IDEs
  22. Xdebug for remote server not connecting
  23. Undefined class Route (Laravel in PhpStorm)
  24. PhpStorm saving with Linux line ending on Windows
  25. Xdebug ignores breakpoints
  26. PhpStorm 2020.2 – PHP Built-in functions are not recognized
  27. While I am debugging PHP Script in Eclipse, it doesn’t load mysql extension
  28. Xdebug V3 doesn’t stop breakpoints in VSCode
  29. WebStorm/PhpStorm double quotes in TypeScript auto import
  30. Stop PhpStorm from aligning associative arrays

Leave a Comment