It has been a while, and I have sometimes got xdebug integration to work, and sometimes not. Then I got busy with other stuff...
I recently got back to some php debugging, and configured slickedit with the a new project connecting to our production server, and everything worked perfectly.
Buoyed with the success, I thought I would have a go at a development job on our test server, and again, it worked perfectly... for a couple of days, then the debugger ceased to stop at breakpoints and became generally unusable, which was where I got to 6 months ago.
This time however, I had one project that still works and one that doesn't, and a capture of some xdebug logs seems to give a big clue as to the problem:
On the server that works, setting a breakpoint gives this in the log:
<- breakpoint_set -i 24 -t line -s enabled -f file:///var/webs/forums/fcf/forum/download/file.php -n 92
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="breakpoint_set" transaction_id="24" state="enabled" id="265870002"></response>
Which has a sensible path on the Linux server, but on the other server, we get:
<- breakpoint_set -i 23 -t line -s enabled -f file:///C:/Users/Mike/Downloads/fcf/fcf_dev_316/forum/ext/anavaro/postlove/event/main_listener.php -n 23
-> <response xmlns="urn:debugger_protocol_v1" xmlns:xdebug="http://xdebug.org/dbgp/xdebug" command="breakpoint_set" transaction_id="23" state="enabled" id="174480001"></response>Which is the local path on the windows machine running Slickedit.
I have checked and rechecked the path mapping in the project/project properties/options pane in SE, but it doesn't help.
It is puzzling that it worked for a while with this configuration and then (apparently autonomously) it stopped working.
Any hints to get the remote file path working?
BTW, still using SE v17, but now with windows 10 64 bit.