When you have quite a lot of plugin code to debug you need to use something like Firebug or Chrome's console. For this you need to use uncompressed .js files. Could someone please explain how to run with these?
I have tried replacing the call to ckeditor,js in samples with source/core/ckeditor.js but that doesn't work. Looked in the developers guide too. As it is (probably because of errors in my code) I get no useful information about what's happening.
Thx. Paul
I have tried replacing the call to ckeditor,js in samples with source/core/ckeditor.js but that doesn't work. Looked in the developers guide too. As it is (probably because of errors in my code) I get no useful information about what's happening.
Thx. Paul
Re: Debugging a Plugin
that's all
Re: Debugging a Plugin
This revealed the following in firebug:
So my problem is that my plugin.js is not coming over the wire intact. It appears to be a straight ascii file and looks ok if you browse to it. However, firefox and chrome see it as gobbledegook.
(My html file for testing is copied from other samples - has a content-type metatag)
Just posting here in case there's any other explanation I haven't thought of.
Thx for any inspiration.
Paul
PS. The second error may be a real problem in one of the official plugin.js files - I'll look into that when I've sorted the bigger issue. The other 2 are probably consequential.
Re: Debugging a Plugin
Anyway, now looking for these three points:
Uncaught [CKEDITOR.editor] The instance "editor1" already exists. editor.js 468
plugins.js:96Uncaught TypeError: Cannot read property 'langEntries' of null. plugins.js 96
editor.js:319Uncaught TypeError: Cannot read property 'en' of undefined editor.js 319
NB. plugins/htmldataprocessor/plugin.js also has a reference to "in dtd[i]" which is thown out. Temportrily commented that out as it looked to be inessential
With any luck I'll crack these by searching the forum.