I could not get filemanager working. When pushing a picture icon and then "Browse Server" button I get this message: "The server didn't reply with a proper XML file\nCheck your configuration". When running http://10.1.8.166/FCKeditor/editor/file ... owser.html
it prints
The server didn't reply with a proper XML file
Check your configuration
Requested URL:
http://10.1.8.166/FCKeditor/editor/file ... d=GetFolde
rsAndFiles&Type=Media&CurrentFolder=%2F
Response text:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head>
<title>Index of /FCKeditor/editor/filemanager/browser/default</title>
</head>
<body>
<h1>Index of /FCKeditor/editor/filemanager/browser/default</h1>
content of folder sent by apache follows
FCKeditor sends request to folder. strange. I reviewed all the configuration files and still have no idea of what goes wrong.
Thanks for support
Mon, 04/02/2007 - 05:55
#1
RE: Filemanager not working: not a proper XML
RE: Filemanager not working: not a proper XML
Also, check for uppercase folder names (eg Image), as now they use strtolower() in the folder defs in io.php. if you remove strtolower(), it will probably work if you can't change your folders to lower case.
RE: Filemanager not working: not a proper XML
in front of all "<?php" statements.
may be screwing some things up.
RE: Filemanager not working: not a proper XML
Those funny chars are causing this problem! You need to fix the corrupted files then the image browser will work (it works for me). For more info on corrupted files in the dist packages, see my post at http://sourceforge.net/forum/forum.php? ... _id=257179
RE: Filemanager not working: not a proper XML
All upper bugfixes didn't have any effect, the bug is still there and the filemanager doesn't work.
I have checked the "...editor/filemanager/browser/default/browser.html" with the Javascript-Console from Firefox, and there is reported the following error:
selectElement has no properties
/fckeditor/fckeditor/editor/filemanager/browser/default/js/common.js
Line: 36
Could that be a reason for the problem? Hav anyone an idea how to fix it ?
RE: Filemanager not working: not a proper XML
The real problem with this is that the files are saved in utf-8 format when they should be saved in utf-8 no BOM format.. that's why you get those errors. Im not sure why they decided to do this since it's pretty much screwed all new installs for us
The way to fix it is by resaving those files in the same directories as your config files all as utf-8 no BOM and you'll be good to go.
RE: Filemanager not working: not a proper XML