This name will be shown in the list of the available run/debug configurations. Specify the run/debug configuration name in the Name field. If you are not sure which template to choose, refer to Run/debug configurations dialog for more information on particular templates. The list shows the run/debug configuration templates. In the Run/Debug Configuration dialog, click on the toolbar or press Alt+Insert. Alternatively, press Alt+Shift+F10, then 0. Create a run/debug configuration from a templateįrom the main menu, select Run | Edit Configurations. The list of available templates varies depending on the installed and enabled plugins. PhpStorm provides run/debug configuration templates for different languages, tools, and frameworks. Select a temporary configuration in the run/debug configuration switcher and then click Save Configuration.Īlternatively, select a temporary configuration in the Run/debug configurations dialog and click on the toolbar. Save a temporary configuration as permanent Save a temporary run/debug configuration as permanent.Ĭreate from a template or copy an existing configuration. PhpStorm provides the following ways to create a permanent run/debug configuration: Create permanent run/debug configurations If necessary, you can increase this limit in Settings/Preferences | Advanced Settings | IDE | Temporary Run/Debug configurations limit. The older ones are automatically deleted when new ones are added. The maximum number of temporary configurations is 5. Permanent configurations have opaque icons while the icons of temporary configurations are semi-transparent. So whenever you run/debug or test your code, PhpStorm either uses an existing permanent run/debug configuration or creates a new temporary one. Permanent configurations remain as part of your project until you remove them.
Permanent- created explicitly from a template or by saving a temporary configuration. To call the context menu, right-click an object or an area. Temporary- created every time you select Run from the context menu. There are two types of run/debug configurations:
Each configuration is a named set of startup properties that define what to execute and what parameters and environment should be used. If I set xdebug.start_with_request = yes in php.ini then debug will work even for Run (or when executing that PHP script outside of IDE) - as long as "phone handle" icon is green (IDE listens for incoming debug requests).PhpStorm uses run/debug configurations to run, debug, and test your code. As you may see these old style parameters do not affect Xdebug 3 at all. That's what IDE is executing: E:\Projects\php\php74\php.exe -dxdebug.remote_enable=1 -dxdebug.remote_mode=req -dxdebug.remote_port=9001 -dxdebug.remote_host=127.0.0.1 E:\Projects\web\_idetest\test.php. (I have a bit mores settings, but those are customisation for output file names, log locations, extra stuff for quickly turn on some options in some scenarios/when needed etc - these are not needed here and it works fine without them)ĬLI debug initiated from IDE ("PHP Script" type of configuration): This is my php.ini content for Xdebug 3 settings (as simple as this): Yes, IDE sends old-style parameters when initiating debugging for a CLI script (like xdebug.remote_ etc) but the debug still works just fine. and it still works fine in PhpStorm 2020.2.3.
I have downloaded Xdebug 3.0.0beta1 for my PHP 7.4 on Windows 10, configured it from scratch (using correct Xdebug 3 config values: and ). It is already supported in the most recent EAP #6 build: check this blog post for more info: Xdebug 3 will be fully supported in PhpStorm 2020.3 version only, which is currently in EAP stage (Early Access Program) and will be released in about 1 month time.