I'm running CKFinder 2.3 (with a license) with PHP 5.3.2 on Ubuntu Lucid and I'm getting an XML error on load. I would normally suspect a server-side problem, but it works in some browsers but not others. It works fine in Safari (Mac & Win), IE, and Opera, but Chrome (22) and Firefox (15) give an error when loading the top level folder (the default view), and occasionally (but not always) when fetching the folder list:
It was not possible to load the XML response from the web server. The server returned an empty response. XML Parsing Error: no element found Location: https://www.example.net/ckfinder/ckfinder.html?action=js&func=ShowFileInfo&dts=1&id=ckf1 Line Number 1, Column 1
Re: XML error in Firefox & Chrome
Re: XML error in Firefox & Chrome
I have a feeling you're answering some other question?
Re: XML error in Firefox & Chrome
With regards to your original question, I haven't seen such problem.
In this case I would start debugging with Fiddler to check if there's a difference between the data sent by each browser and how messing with those differences affect the response by the server.
Re: XML error in Firefox & Chrome
I have installed 2.3 but did not fixed it..
Re: XML error in Firefox & Chrome
In case of a blank page always turn on error reporting and display errors (unless you're on a production site and can't do this).
The blank page/response suggest a PHP error and without knowing what is the problem, it's hard to suggest the solution.
You may try enabling error reporting and display_errors in ckfinder/core/connector/php/connector.php
Wiktor Walc
CTO, CKSource - http://cksource.com
--
Follow CKEditor on: Twitter | Facebook | Google+
Re: XML error in Firefox & Chrome
That is a truly weird error - is_dir is an internal PHP function that has nothing to do with sessions (and I don't have my own implementation lurking somewhere)! I had a similar error from rmdir too.
It's difficult to get into the right context to debug (with XDebug in PHPStorm) the CKFinder XHRs, though I eventually managed it by extracting the URLs with the web inspector and running them in the same browser session; I didn't manage to come to any useful conclusion though. I can only conclude that there's something wrong with PHP on that server.
The same code running on a different server does not have the same problems with CKFinder, so I've switched to that and I'm going to ignore it now.