hi all
i have just installed the ckeditor 3.0 after upgrading from the fckeditor 2.0.
i am now getting a message about insecure content on a secure page. i have not been able to find any info on this topic for version 3.0. a similar problem with version 2.0 had been fixed long ago.
the script is obviously sourcing some content with http: instead of https: - i guess?!
has anyone out there had this problem or has come across the appropriate documentation?
any help would be appreciated.
Wed, 10/28/2009 - 05:10
#1
Re: insecure content on secure page
I think that it's caused by the spellchecker. The problem could be fixed by automatically deactivating the spellchecker if the ckeditor instance is loaded from a secure page (https) ... even if there was a secure spellchecker, you probably don't want text entered on a secure page to be transmitted to a spell checker website ...
Re: insecure content on secure page
yes, you are right. i checked the headers and it is coming from the spell checker. ( i obviously missed this originally because, i did check, but not well enough)
i might be missing something, but, after a search here and a general web search, i could find no documentation on disabling plugins in general and the scayt system in particular.
i am sure it will be a simple process through the api but but my attempts to do it so far have failed.
you would not happen to know it?
Re: insecure content on secure page
^ sorry, but no ... I was hoping that some experienced CKeditor coders could help us out. Well, they should if they want to see their creation used on business websites ...
But I'm not in too much of a hurry ... it would be nice though if the bug could get fixed in the next months or so.
Re: insecure content on secure page
It would be ideal if there a config value that would switch off the spell checker so that users did not receive a warning message about insecure content.
Re: insecure content on secure page
Re: insecure content on secure page
i will try again and let you know how it went.
cheers rs
Re: insecure content on secure page
just a couple of notes on configuring the API by removing the spelling checker:
Make sure you replace "editor" in the code with the name of your text area
You may already be configuring the editor so just add the removePlugins line after a comma . I know this is basic, but things easier than this have stuffed me up before.
also, if you have uploaded the new version, make sure you clear your cache to get the latest version of the editor. .js files are often cached
also the news is not all good as, after I removed the plugin, i checked to see if it was really working. I discovered that initially, if the plugin is included, but scayt is not activated it did not show that there was insecure content on the page
once i activated scayt through the toolbar, the icon indicating insecure content, switched itself on without the page reloading. i am not too sure if an alert pop up also results (mine in not switched on).
Re: insecure content on secure page
Re: insecure content on secure page