Presenting a way to debug file browser

I found it very annoying never to understand what the file-browser was doing in all that xml-communication used, especially as I and many others have had problems configuring the correct paths to use! (Gave me a 2h head-ache...)

For me the FCK debug-mode did nothing helpful in this matter...

This is the way I found out what was happening behind the scene. In editor/filemanager/browser/default/browser.html I added "
// For debug
prompt("Url used", sUrl);
" as below:

...
oConnector.SendCommand = function( command, params, callBackFunction )
{
var sUrl = this.ConnectorUrl + 'Command=' + command ;
sUrl += '&Type=' + this.ResourceType ;
sUrl += '&CurrentFolder=' + escape( this.CurrentFolder ) ;

if ( params ) sUrl += '&' + params ;

// For debug
prompt("Url used", sUrl);

var oXML = new FCKXml() ;

if ( callBackFunction )
oXML.LoadUrl( sUrl, callBackFunction ) ; // Asynchronous load.
else
return oXML.LoadUrl( sUrl ) ;
}
...

This allows to copy-paste the url used by the connector into a new browser-window and see the xml-response.

Hope this helps.