I have tried to set up Xdebug (2.2.3) with PhpStorm 7.0 and I cannot bring up the step-through debugging console as I have in the past. The guides that I have used to set this up are:
- https://www.jetbrains.com/phpstorm/webhelp/configuring-xdebug.html
- http://blog.jetbrains.com/webide/2011/02/zero-configuration-debugging-with-xdebug-and-phpstorm-2-0/
I know that the Xdebug extension itself is working as the cachegrind.out.3280 files are being created on page load (with 12Mb litany of all of the scripts required and variables/values). My set up in php.ini (php version 5.4.12) is:
zend_extension="c:/wamp/bin/php/php5.4.12/zend_ext/php_xdebug-2.2.3-5.4-vc9-x86_64.dll"
xdebug.profiler_output_dir="c:/wamp/tmp"
xdebug.profiler_output_name="cachegrind.out.%p"
xdebug.profiler_enable=1
xdebug.remote_enable=1
xdebug.remote_port=9000
xdebug.idekey=xdebug
xdebug.remote_connect_back=1
xdebug.remote_host=dashboard.dev
After setting a break point, turning on Xdebug chrome extension, clicking to listen to Xdebug within PhpStorm and refreshing, I get the Incoming Connection from Xdebug dialogue:

However, when I click Accept, the dialogue disappears and nothing happens.
If I then go to Settings / PHP / Servers in PhpStorm, I see that a new entry has been created:

Only by deleting the entry that was added can I get the Incoming Connection dialogue to show up again when I refresh the page. I notice that the port is set to 80 so wondering if that is right since the Xdebug extension is set to run over port 9000; when I click "Validate remote environment" select deployment server, then "Validate", I get: No debug extension is loaded. So I am assuming that the problem is something related to how this is set up.
xdebug.remote_host=dashboard.devthat's actually wrong -- it should be your IP address / domain name, not your website domain. it works only because it points to the same IP as your computer (127.0.0.1). 3) "Only by deleting the entry that was added can I get the Incoming Connection dialogue to show up again" -- that's correct and works exactly as it should.phpinfo();when executed via web interface (in a browser). Af far as I see it so far -- it should work for you OK -- I mean, it picks up incoming debug request. So .. what's happening after -- does it breaks on breakpoint? What will happen if you putxdebug_break();in your code (programmatic breakpoint) ?phpinfo()output -- it should tell whatArchitectureyour PHP is.