I didn't notice anything about this in the xdebug thread, but I found that setting the Xdebug file directory from the options will clear the php.ini file of all information except for the active settings.
This is a great "feature" if wishing to determine a specific setting, but makes it hard if wishing to turn on a setting in the future. I had to go back to the installation and extract the php.ini file. Which then, I had to go through and turn some things on and remove the extra debug extension. I have now made a copy of it for easy restoring.
I was trying the debugger and had noticed debug wasn't working. The Xdebug DLL directory was blank, so I set it and then checked the php.ini file. It had only the active settings. (The reason the debugger wasn't working was I had dragged a file from outside the local server path directory for temporary viewing. Guess it can't debug from outside its area!) Not sure why the xdebug path was blank or what difference it makes. It seems to work either way (if using a file in its server path!). I notice the current cursor pointer while debugging doesn't show. But, then, I STILL have had a hard time understanding how the debugger works, so I don't know.
*Inserting the path will add the duplicate zend path at the xdebug section*
Maybe that's why it makes no difference for a blank path or not? Maybe what caused part of ddp_ludo's problem?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I didn't notice anything about this in the xdebug thread, but I found that setting the Xdebug file directory from the options will clear the php.ini file of all information except for the active settings.
This is a great "feature" if wishing to determine a specific setting, but makes it hard if wishing to turn on a setting in the future. I had to go back to the installation and extract the php.ini file. Which then, I had to go through and turn some things on and remove the extra debug extension. I have now made a copy of it for easy restoring.
I was trying the debugger and had noticed debug wasn't working. The Xdebug DLL directory was blank, so I set it and then checked the php.ini file. It had only the active settings. (The reason the debugger wasn't working was I had dragged a file from outside the local server path directory for temporary viewing. Guess it can't debug from outside its area!) Not sure why the xdebug path was blank or what difference it makes. It seems to work either way (if using a file in its server path!). I notice the current cursor pointer while debugging doesn't show. But, then, I STILL have had a hard time understanding how the debugger works, so I don't know.
*Inserting the path will add the duplicate zend path at the xdebug section*
Maybe that's why it makes no difference for a blank path or not? Maybe what caused part of ddp_ludo's problem?