Installing xdebug and using 3rd party IDEs requires no mediawiki side debugging, just modules installing onto the running php config and reloading the webserver

mdale wrote:

yes xdebug lets you see the debug requests in a debugger outside of the browser, the bug was about firebug integration with the firephp add-on in the browser. Makes it a little easier to keep track of where things went wrong when the debug information is matched up per your many ajax requests automatically.

But this is obviously a low priority bug, since you can practically do the same thing with the tool set you describe or just tail a temporary file that wfDebug outputs. ( Its just less convenient and you have to manually sync up the several ajax requests with your javascript debugging lines )

Added FirePHP extension in r88843; had to add a 'Debug' hook from wfDebug & wfDebugLog() to handle it.

Note that a few messages at top or bottom don't get output due to being too early for extension initialization or too late for HTTP headers.

mdale wrote:

sweet! Thanks Brion, I bet this will be helpful for ajax RTE efforts too ;)