The forum operates in read-only mode.
Please head to StackOverflow for support.
I am getting Error: this.DOMDocument has no propertiesSource File: http://localhost/vfweb/admin/coms/fcked ... gecko_2.jsLine: 20while integrating FCKEditor with netscape 7.Please help
>Hey,>>I'm writing you this mail because i found a solution you>posted here for the this.DOMDocument problem with FCK editor:>>http://sourceforge.net/forum/message.php?msg_id=3171212>>Now i don't know exactly what you did to solve the problem,>can you tell me or post it in a message at that forummessage?>>Thanks in advance, >>Ronald OldenburgerAre you using an older web server? My problem was that when the XML data was send, the server was not sending the proper MIME type. All I had to do was add it to the webserver configuration to send the text/xml MIME type header for that content type and it worked after that.If you're using a more recent webserver (say 1-2 years old), then this is most likely not the same problem.Good luck!Gary
I had this same problem and just spent 2 hours hunting it down. Turns out it was my webserver configuration. What was happening was that when the editor uses XMLHttpRequest() to retrieve the styles XML file from the webserver, my webserver was returning the XML file without the proper MIME type, and XMLHttpRequest object does not like that at all. You see, I was using a much older web server which did not have "XML" mime type defined yet. All I had to do was add XML as text/xml mime type and now it's all good.I hope this is your problem, it's an easy fix.
I'm having a similar issue, running IIS 6 on a Win2k3 server. I've set the mime type for the site (.xml text/xml) and am still unable to view the file (FCKEditor/fckstyles.xml) directly in either Firefox 1.5 or IE 6.This particular server is shared and is managed by HostMySite.com, so I have very little access to it. The techs are still struggling with this issue. We can view some xml files directly in a browser, but when we move the same file to a different directory, we cannot view it anymore. It seems to be a weird mime mapping issue that has us all stumped.When this file (fckstyles.xml) is deployed on my own dedicated production server, I *can* view the contents of this file directly in both Firefox and IE. This tells me that mime types are configured differently between my dedicated server and this HostMySite.com shared server.Okay, here's the kicker... Using IE 6, even though I cannot view the contents of the fckstyles.xml file, the editor still appears to loads correctly. Perhaps that's because when I view source on the browser request made to the fckstyles.xml file, I get the following HTML code (I hope it displays in this post):<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<META http-equiv=Content-Type content="text/html; charset=utf-8"></HEAD>
This content seems to be enough to bypass the "DOMDocument has no properties" error. However, I noticed that no styles appear in the styles menu of the editor.If anyone has any ideas why IIS 6 would server an xml file in one directory, and then fail to serve the exact same file in a subdirectory, please share.