Further I thought DrByte suggested turning off the ENABLE_SSL_ settings, which you've currently only done at this point on the catalog side.
Printable View
Further I thought DrByte suggested turning off the ENABLE_SSL_ settings, which you've currently only done at this point on the catalog side.
If you tell me what you want to see it is easyer.
The lines you quoted are there because of google.
They will disappera as soon as I will switch to 1.5.5 responsive.
However they have nothing to do with ssl and the admin side.
Ciao
Thanks.Quote:
Further I thought DrByte suggested turning off the ENABLE_SSL_ settings, which you've currently only done at this point on the catalog side.
I did not realize that DrByte suggested to do it also on the admin config. I did it now, but nothing changed. CKEDITOR still does not get loaded, while HTMLAREA does.
In my opinion is a matter of configuration on CKEDITOR, but I have no idea of how to change it.
ciao
enzo
Use your browser's javascript console to look at what errors javascript is encountering. Also use the browser's error-reporting to see what errors it's encountering related to SSL on those pages. Those will give you clues about how to fix whatever is not loading properly and why.
Thank again for your help.
This is what happened.
I used the console and found that the php handler was giving errors. (ckeditor.php)
I uploaded the handler from 1.5.4. but nothing changed.
Always using the console, I then found another error in the ckeditor.js
Uploaded ckeditor.js from 1.5.4
Nothing changed, but it got even worse because also the editor's frame disappeared and ckeditor did not work anymore even without ssl.
Uploaded from a back up on one day before the whole editor folder and magically both editors started working again with ssl active.
Probably the problem was a corrupted file, but:
It sounds very strange to me that the file got corrupted right after setting ssl for the admin.
It sound even strange that the file corruption interested only the ssl setting and not the plain setting given that it did work perfectly switching form ssl to plain.
Software mistery....:shocking:
P.S. While typing my brain was knocking at me and I realized that it could be a cache problem. I can not tell exactly but I am shure I cleaned the cache at a point in the process above, but I am also sure I cleaned it even before starting using the console.
Opinions welcome!!!!
Ciao from Italy
enzo
Thanks for reporting back that re-uploading the plugin's files resolved the problem.