XML -- help with image upload/resource browser XML request

Download the latest version fo FCKeditor (2.6RC at this moment).
Check if the problem still occurs.

I have the exact same problem, except I think it also happens in firefox as well for me...no seems to know the answer so far...

viewtopic.php?f=6&t=9092

I the xml error code is the same and when it pops up as well, but it is indeed a different source...my config files are all unchanged and default and all the necessary directories have been chmod to 666 so I have no idea what's going on in my case, in that past thread, it references a problem on line 37 which I posted for anyone to look at to help diagnosis the problem, I think 2.5.1 is what comes with tikiwiki 1.10 so maybe upgrading all the files from the 2.6RC would fix things...

I had a similar error which I could trace back to the asp-connector of the filebrowser. It looks like the problem has only been fixed for php in version 2.6rc as it persists in 2.6 with asp.

For those who are curious where the problem comes from:
When you look into the response text you can see some special chars which can't be displayed i.e.: <File name="Diese?ag_Web.jpg" size="164" />
Obviously the server doesn't send the XML-data correctly in UTF-8 format. Firefox ignores these errors in the XML-data and shows the list (but you can't add Diese?ag_Web.jpg to your editor box), IE refuses to accept the data completely. You can verify this by entering the URL which is shown under: "Requestet URL" into IE. You should get an error message complaining about wrong characters.
For asp there is a bug in the /editor/filemanager/connectors/asp/basexml.asp, the charset ist set with:

Response.CharSet = "UTF-8"

but the required

Response.CodePage= 65001

is missing.

Add this line to basexml.asp and everything is fine.

Check the file names. It looks like you have those little squares from special characters in the file names. In our case, we had this error when there was a file named:

filename….pdf

the %85 special character of ... in the filename triggered this error.

Best wishes,
Emma