Dear Tobias... I understand that it's frustrating when you are trying to achieve something with no success. As a suggestion, please try to be gentle when posting messages and asking for help. People would be much more responsive in this way.
Anyway, back to your post.
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!).
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.
When are people going to stop forcing their users to register for every major fart?!
You have really answered... so here is the answer: In the day people will stop with vandalism and spamming.
So, what's causing this? Can I rewrite "this.DOMdocument" to something more sensible? If yes, to what?
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.
That error can happen only if the call to the server connector doesn't return a proper response, and it's totally unexpected. Next version will handle more gracefully that situation, but the point is that the call to the server isn't returning something valid, so the best option for the moment could be to use Firebug and find out what's wrong with the response sent by the connector.
Well, I had the same problem with this.DomDocument. When I looked in my error logs I saw that it was forbidden to use "eval" in php. My webserver works with Suhosin en that was the reason the use of "eval" was forbidden. I edited my suhosin ini file with "suhosin.executor.disable_eval 0" and YESS!!! it worked.
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
Re: this.DOMdocument has no properties
Re: this.DOMdocument has no properties
I hope this will help.