The editor script loads spellchecker related files from an external website (http://...) which causes browsers to mark the whole page as insecure (e.g. red exclamation mark on the SSL symbol).
I guess I could simply deactivate the spell checker somehow, but it would be really cool if the editor would simply not load it on SSL-encrypted pages.
BTW: There's another thread about this problem - I just created this thread because the subject line is a bit more precise.
Wed, 11/11/2009 - 17:01
#1
Re: CKEditor 3.0 doesn't work properly on SSL-encrypted pages
Come on - nobody else uses CKEditor 3.0 on SSL-encrypted pages?
Re: 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
Re: CKEditor 3.0 doesn't work properly on SSL-encrypted pages
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?
Re: CKEditor 3.0 doesn't work properly on SSL-encrypted pages
Also looking for a solution on this.
Andy
Re: CKEditor 3.0 doesn't work properly on SSL-encrypted pages
Does anyone know whether there's a chance for this to get fixed (possibly with 3.0.2)?
Re: CKEditor 3.0 doesn't work properly on SSL-encrypted pages
Re: CKEditor 3.0 doesn't work properly on SSL-encrypted pages
Re: CKEditor 3.0 doesn't work properly on SSL-encrypted pages
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: