insecure content on secure page

thanks for your reply...

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?

thanks for the tip. i actually tried what you suggested (after the original post), but i probably had the syntax wrong.

i will try again and let you know how it went.

cheers rs

good news on a couple of fronts. not only did yavin's tip work (thanks mate!), but it appears that they have at least partially fixed the bug that was making an insecure header being sought and sent. you will need to upload the latest version (3.2) which was just released a couple of days ago.

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).

my mistake - version 3.1