Php – Xdebug 3 – The setting ‘xdebug.remote_***’ has been renamed, see the upgrading guide

PHPphpstormxdebug

I just installed Xdebug v3.0.0beta1 on my OSX and tried to use it on PhpStorm 2020.1, but I get this :

Xdebug: [Config] The setting 'xdebug.remote_enable' has been renamed,
see the upgrading guide at
https://xdebug.org/docs/upgrade_guide#changed-xdebug.remote_enable
(See: https://xdebug.org/docs/errors#CFG-C-CHANGED) Xdebug: [Config]
The setting 'xdebug.remote_host' has been renamed, see the upgrading
guide at
https://xdebug.org/docs/upgrade_guide#changed-xdebug.remote_host (See:
https://xdebug.org/docs/errors#CFG-C-CHANGED) Xdebug: [Config] The
setting 'xdebug.remote_mode' has been renamed, see the upgrading guide
at https://xdebug.org/docs/upgrade_guide#changed-xdebug.remote_mode
(See: https://xdebug.org/docs/errors#CFG-C-CHANGED) Xdebug: [Config]
The setting 'xdebug.remote_port' has been renamed, see the upgrading
guide at
https://xdebug.org/docs/upgrade_guide#changed-xdebug.remote_port

And the links provided lead to nothing but an image with bugs.

My question is what are the right settings to set and where to actually change them since i have nothing about xdebug in my php.ini file.

Best Answer

PhpStorm 2020.3 supports XDebug3. There is a detailed upgrade guide on how to change your settings properly.

In my case (using Docker), I had to change the settings

from:

; v2.*

[Xdebug]
zend_extension=xdebug.so
xdebug.remote_enable=1
xdebug.remote_autostart=1
xdebug.remote_connect_back=off
xdebug.remote_host=host.docker.internal

;# 9000 is default (not required to set).
xdebug.remote_port=9000

to:

; v3.*

[Xdebug]
zend_extension=xdebug.so
xdebug.mode=debug
xdebug.start_with_request=yes
xdebug.client_host=host.docker.internal

;# 9003 is now the default (set this for old PhpStorm settings).
xdebug.client_port=9000

Related Solutions

Settings up xdebug on MAMP PRO

Since release of MAMP 2.01 XDebug is already included.

Solved. Here's the tutorial that helped me:

Start MAMP
Edit php.ini template file through MAMP to enable the extension. Edit the template file via File -> Edit Template -> PHP -> PHP php.ini

Edit bottom of php.ini template file so that it ends up looking like if you want profile output

[xdebug]
zend_extension="/Applications/MAMP/bin/php/php5.3.6/lib/php/extensions/no-debug-non-zts-20090626/xdebug.so"
xdebug.profiler_enable = 1
xdebug.profiler_output_dir = "/tmp"
; DONT REMOVE: MAMP PRO php5.3.6.ini template compatibility version: 1

If you don’t want profile output and just want xdebug running then use

[xdebug]
zend_extension="/Applications/MAMP/bin/php/php5.3.6/lib/php/extensions/no-debug-non-zts-20090626/xdebug.so"
xdebug.profiler_enable = 0
xdebug.profiler_output_dir = "/tmp"
; DONT REMOVE: MAMP PRO php5.3.6.ini template compatibility version: 1

Now when you have errors, if they are sent to standard out, you will see something like this

My php.ini file:

edited php.ini file to run xdebug on mamp mac osx

Save edited template and close edit window
Restart MAMP
Open MAMP’s WebStart page and navigate to PHPInfo tab. Check to make sure that Xdebug is running. Doing a search in the browser window for “Xdebug” makes this easy.
If you used the same settings that I have above, when you run PHP code, Xdebug will put the cachegrind.out files in your ‘/tmp’ directory. Open your ‘/temp’ directory and run one of your PHP files to make sure it is working correctly. You can open the ‘/tmp’ directory in finder by opening the terminal and running
```
open /tmp
```
Now you can use any app that understands those cachegrind.out files to view the profile data. Apps like KCacheGrind (Linux/Windows, KDE), WinCacheGrind (Windows), xdebugtoolkit, and Webgrind. I went the simple route and used webgrind. Webgrind is a simple web based application that you can run locally on MAMP and it will look for the cachegrind.out files automatically with just one click. Continue for steps on setting up with webgrind.
Download Webgrind
Setup Webgrind host on MAMP to run Webgrind
Visit webgrind url setup on your local MAMP installation. Mine was simply webgrind/
If you already have cachegrind output files you should be able to select the file in the “Auto (newest)” dropdown or leave it select at Auto and click update which will reveal the profile data
Throw a celebratory fist pump

Php – Xdebug not working with PHPStorm

Try to configure your project in PhpStorm

Open Settings->Languages & Frameworks->PHP->Debug
Uncheck the "Ignore external connections through unregistered server configurations" option
OK

Best Answer

Related Solutions

Settings up xdebug on MAMP PRO

Php – Xdebug not working with PHPStorm

Related Topic