First of all, the manual for CKFinder is insufficient. Integration with FCKEditor is by no means smooth. Please write manuals with people in mind that are not as capable as you are (like me!).
After finding out how to integrate CKFinder, it didn't come up right. The popup-window opened, it says "Folders" in the top left... but that's it. So I check the Javascript-console and SUPRISE!... there's an error:
Error: this.DOMDocument has no properties
Source: http://www.mydomain.com/PathToCMS/FCKed ... r_gecko.js
Line: 31
So I compare the working (!) demo-versions here on the FCKEditor website and check my JS-console output. No error. Then I played around with multiple lines for the baseURL and baseDir. Nothing. I googled the damn JS-error and spend the next 4h reading & trying. I then have to register in a forum to file a bug-report and create an account I'm very likely never to use again (When are people going to stop forcing their users to register for every major fart?!).
So, what's causing this? Can I rewrite "this.DOMdocument" to something more sensible? If yes, to what? If CKFinder is not working for me - What plugin should I use so that I can delete & rename files with FCKEditor's filebrowser?
For Debugging:
Server: Linux. (theoretiker.org)
Browser: FF2 @ Ubuntu Feisty (and NO, I am not a victim of the Firebug-Bug concerning this.DOMdocument... I checked that already)
Thu, 08/09/2007 - 17:49
#1
Re: this.DOMdocument has no properties
Anyway, back to your post.
We didn't have complains regarding the documentation. Remember that the "_samples" folder is very important to help understanding how to integrate CKFinder. Of course, all those resources are developer oriented. If you have any constructive opinion to give in this sense, you are welcome.
You have really answered... so here is the answer: In the day people will stop with vandalism and spamming.
We did a lot of work to try to transform errors on human understandable messages. Unfortunately you are facing one of those rare cases of unmanaged errors, and it is most likely to be a specific issue in your installation.
A good way to try to debug it is by watching all Ajax responses received by CKFInder with Firebug. If server side errors are involved, you should be able to see some errors there.
Let us know if you was able to solve the problem.
Frederico Knabben
CKEditor Project Lead and CKSource Owner
--
Follow us on: Twitter | Facebook | Google+ | LinkedIn
Re: this.DOMdocument has no properties
Yeah, you're right. But after wasting all that time to get such a simple thing running I was simply going ... So, my apologies for being such an asshole earlier on.
Anyway, the problem remains the same: There's just this one error coming up in the Javascript-console when trying CKFinder on my server. And it does not come up when I'm trying the demo here. So it must be something with the server I'm on.
Massive googling brought up that the server might need to be reconfigures to serve XML right. But I really do not have any influence on the setup of my host.
Can I replace all calls of this.DOMdocument with something else that might work? What is this.DOMdocument supposed to contain? Can't I just replace it with a fixed ID or NAME based upon my installation-environment? Or am I completely off my mark?
Re: this.DOMdocument has no properties
Re: this.DOMdocument has no properties
I hope this will help.