CKEditor 3.0 doesn't work properly on SSL-encrypted pages

As a guess... what happens if you explicit set the CKEDITOR.basePath to be a full url including https (eg. "https://mysite.com/ckeditor")?

Regards,

Rob

Same problem here.
I tried using this setting, but no difference:

CKEDITOR.editorConfig = function( config )
{
// Define changes to default configuration here. For example:
//config.language = 'ru';
// config.uiColor = '#AADC6E';
config.baseHref = 'http://mysite.com/admin/js/ckeditor/';

};

We need this to work with SSL! ANy ideas out there?

ericp wrote:Same problem here.
I tried using this setting, but no difference:

CKEDITOR.editorConfig = function( config )
{
// Define changes to default configuration here. For example:
//config.language = 'ru';
// config.uiColor = '#AADC6E';
config.baseHref = 'http://mysite.com/admin/js/ckeditor/';

};

We need this to work with SSL! ANy ideas out there?

Shouldn't baseHref be https instead of http? Has anyone actually tried an appropriate baseHref config setting?

Also, if you need a work around, just remove the spell check plugin. Otherwise, I guess you could dig into the source of the spell checker plugin and ascertain where it is being loaded and ensure it is being loaded via SSL.

Another solution, which I posted in the related thread, is to just remove the offending plugin:

yavin wrote:
You can use the removePlugins config entry to remove the SCAYT plugin.

This should do the trick:

CKEDITOR.replace("editor",
{
    removePlugins: "scayt"
});

I've got a CKEditor control on an HTTPS/SSL web page. I just today enabled the SCAYT feature and now see a Security Warning when the page loads.

It seems to be caused by these four files:

• http://svc.spellchecker.net/spellcheck31/lf/scayt/_base.xd.js
• http://svc.spellchecker.net/spellcheck31/lf/scayt/nls/caption.xd.js
• http://svc.spellchecker.net/spellcheck31/lf/scayt/lang_list.js
• http://svc.spellchecker.net/spellcheck31/lf/scayt/resources/blank.gif

I found a Ticket #4065 for this issue. SpellChecker.net reportedly corrected the problem from their end 12 days ago.

http://dev.fckeditor.net/ticket/4065

Why do I still see the warning form my web site?