[dokuwiki] Fwd: [fckglite] Re: fckglite not working

  • From: Ted To <rainexpected@xxxxxxx>
  • To: <dokuwiki@xxxxxxxxxxxxx>
  • Date: Fri, 16 Nov 2012 13:56:04 -0500

Hi, the developer for the fckglite plugin posting to the dokuwiki mailing list to see if anyone had any ideas about why the plugin is failing for SSL connections.


Thanks,
Ted To

-------- Original Message --------
Subject: [fckglite] Re: fckglite not working
Date: 11/15/2012 6:57 pm
From: Myron Turner <turnermm02@xxxxxxx>
To: fckglite@xxxxxxxxxxxxx
Reply-To: fckglite@xxxxxxxxxxxxx

From my latest analysis I've concluded that there is something going on with ssl. When I access the page through https, I get the problem with
the blank edit window for Iceweasel and some xml markup for Chromium.
But when I access it with http, fckglite works beautifully.  I'm not
sure why it should matter.

Chromium's developer console gives:

[blocked] The page at https://<URL>/doku.php?id=start&do=edit&rev=0 ran insecure content from http://<URL>/lib/plugins/fckg/fckeditor/fckeditor.js. [blocked] The page at https://<URL>/doku.php?id=start&do=edit&rev=0 ran insecure content from http://<URL>/lib/plugins/fckg/scripts/vki_kb.js.
The page at https://<URL>/doku.php?id=start&do=edit&rev=0 displayed
insecure content from http://<URL>/lib/images/smaller.gif.
The page at https://<URL>/doku.php?id=start&do=edit&rev=0 displayed
insecure content from http://<URL>/lib/images/larger.gif.
The page at https://<URL>/doku.php?id=start&do=edit&rev=0 displayed
insecure content from http://<URL>/lib/images/wrap.gif.
Uncaught ReferenceError: FCKeditor is not defined


I'm not sufficiently knowledgeable about ssl. So, I can't explain the insecure content coming from lib/images, since that should be covered by the same certificate that covers your dokuwiki installation.

I do have a possible idea about the fckeditor problem (although again I can't speak with certainty). The fckEditor runs in an IFRAME, which makes it in effect an independent web site; this is even clearer with the fckEditor's file-browser, which opens as a separate window, with its own URL in the location bar. So, it's possible that the browser sees the fckEditor as an unsecured intrusion.

Unfortunately, I don't know of anyone else using fckgLite with ssl; but if no one on this list has a solution, you should try the dokuwiki forum.

--
Myron Turner
http://mturner.org/
http://mturner.org/fckgLite
https://github.com/turnermm
------------
fckgLite list archive:
//www.freelists.org/archive/fckglite

Manage your subscription:
//www.freelists.org/list/fckglite

fckgLite web site:
http://www.mturner.org/fckgLite/doku.php

Asking Questions
http://www.mturner.org/fckgLite/doku.php?id=faq#asking_questions
--
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist

Other related posts: