The forum operates in read-only mode.
Please head to StackOverflow for support.
This is a known problem with Firefox 3 when FCKeditor is opened from the local filesystem: https://dev.fckeditor.net/ticket/1645.The issue is caused by a new security check implemented in Firefox 3 for file:// URIs. It can be disabled by going to about:config and setting security.fileuri.string_origin_policy to false.See the following Mozilla documentation for more information: http://kb.mozillazine.org/Security.file ... gin_policy
martinkou wrote:It can be disabled by going to about:config and setting security.fileuri.string_origin_policy to false.
A.M. wrote:martinkou wrote:It can be disabled by going to about:config and setting security.fileuri.string_origin_policy to false.A typo. Should be security.fileuri.strict_origin_policy
DarthSonic wrote:A.M. wrote:martinkou wrote:It can be disabled by going to about:config and setting security.fileuri.string_origin_policy to false.A typo. Should be security.fileuri.strict_origin_policyThe developers of Firefox got a reason to secure this, so I would not prefer to disable it to get a workaround! I am waiting for a fix.
DarthSonic wrote:The developers of Firefox got a reason to secure this, so I would not prefer to disable it to get a workaround! I am waiting for a fix.
So, if you opened something like ../some_dir/some_html.html in the child iframe, Firefox 3 will determine that they are not from the "same origin" even though they belong to the same code package (e.g. FCKeditor, or Dojo, or YUI, etc.), and thus FF3 will give out permission errors.It is clearly written in the MozillaZine document I gave you that "If you do development with local files and need to be able to retrieve other local files, you may need to set this preference to false". So disabling this security check for local web development is pretty much a standard practice in Firefox 3. Also, since the security check applies to file:// URL only, there shouldn't be any way it can be exploited by malicious remote websites, so the security risks posed by disabling the strict origin policy setting should be minimal.
alfonsoml wrote:At the current state of the restriction made in Firefox, it's impossible to make this work without rewriting everything to change all the locations of the files (and even then I'm not sure if it would work)
nemlah wrote:Hey guys,We have some trouble with FF3 and FCKEditor as described in these post, but the About:config entry in FF3 is not working and we still get the same error.The problem is that the errorFCKeditorAPI is undefineddoesn't always occur. First visit on the site works ok, the following visits seem to trigger the error. The problem description got me thinking that maybe something is screwed with js loads. Whenever it breaks it seems ff is using the files from the cache..Any help is appreciatedVasilis
I was having this same problem, but not at a file:/ url - on a real live site.I think I've found a solution, thanks to http://dev.fckeditor.net/ticket/1907: simply change
on line 38 of editor/js/fckeditorcode_gecko.js. The editor continues to work fine in FF2 and 3, and I was no longer able to reproduce the problem. YMMV, but HTH.
I've posted a patch to https://dev.fckeditor.net/ticket/1907. If there are no unexpected troubles, the fix should be included in FCKeditor 2.6.3.
hi, I think i'm having the same kind of problem, and i'm not using the newest fckeditor sooo .. i cant change the file fckeditorapi.js, simple cuz the line isn't in it, i get some different error tho, but i think its related too the same problem could any1 help me out, and don't answer with update too the newest fckeditor please ....here is the error i get in the errorconsole of firefox, i try too add a hyperlink with the fckeditor btw ... I tested it in IE and there it worked soo there has too be a solution for this no .... Error: uncaught exception: [Exception... "Node cannot be used in a document other than the one in which it was created" code: "4" nsresult: "0x80530004 (NS_ERROR_DOM_WRONG_DOCUMENT_ERR)" location: "http://.../FCKeditor/editor/js/fckeditorcode_gecko.js Line: 38"]Anyway thanks on advance
jainasewen wrote:firebug causes it, try disabling firebug for the page that the editors are on and see if that solves the problem