FCKeditor producing errors in IE

I may be experiencing a similiar issue, and I believe it's related to a recent MS security update. Investigating further...

I am having the same issue. I will explain in a bit more detail on mine. I have a DIV tag with the script inside it developing on my local machine. In IE6+ on my local machine the DIV tag will display and any data in it will display with trhe exception of the FCKEditor. I get all sort of warnings regarding features not being identified. The exact same program on my local machine but through FireFox produces no errors and works as expected.

Now, if I promote the same code up to my server and then try to access it from the IE it all works with no issues and no javascript warnings. Same for FireFox. I only get the error when developing the code locally. Makes it challenging to locally test via IE before promoting code into production. We are an IE shop, and while I could tell all developers to test via FF it makes for poor development to push up content without first being sure that it works in a development computer via the user's browser choice which again is IE.

Any ideas why it would fail locally but not remotely?

My only suggestion would be to use the IE8 developer tools to debug the script and find out what's wrong.

alfonsoml wrote:My only suggestion would be to use the IE8 developer tools to debug the script and find out what's wrong.

Have been doing that but so far have not seen any errors and again, this only happens if in local filesystem. It works as expected in http://localhost or any other website I place it on. Do not recall ever seeing a javascript that worked differently on a local file system than a server.

IE applies different rules to pages according to the zone where they are located, so it doesn't sound impossible that running it from a local filesystem has some strange behavior.

I just don't understand why don't you use a local server to test the website instead.

alfonsoml wrote:IE applies different rules to pages according to the zone where they are located, so it doesn't sound impossible that running it from a local filesystem has some strange behavior.

I just don't understand why don't you use a local server to test the website instead.

A local server is not fully working as well for the project at large. Granted, in my little test area where I am exploring how to make all of this work before adding it to the actual project is an option but in the grand scheme of events it will not be a solution going forward. Now keep in mind that it is not FCKeditor exclusively with this issue as I can again do a simple code just like I am attempting in a static HTML file and it works exactly as expected, even from the local filesystem. It is only when I move these features into my Adobe Flex application that I see this behavior. Again, only in IE (6,7,8) and only from the local filesystem. I am exploring other issues such as sandbox security rules for Flash Player (which Flex uses) as well as other areas but also not ruling out that it may be something in the scripting errors that may help me lead to the fix. Somewhere it is a combination of FCKEditor, Adobe Flex (Flash Player), IE and the local filesystem that is causing the error.

In doing some additional digging I see this block of code in the FCKeditor.html file. Now it makes a reference to the exact issue I appear to be having for IE but of coruse it is referenceing FF3, and a warning of what to do in FF3 to make a correction. Could this be a case of the editor having a like situation for IE with regards to my special need for it to be used? The strange thing is that have tested my code on FF3 and never received any issues no have I made any changes, as suggested in the code block for correction. In any event, this would appear, at least to me, to be the same issue I am seeing for IE when trying to use FCK in a DIV block displaying over a SWF file. Any thoughts? Still struggling to make this work correctly.

// #1645: Alert the user if opening FCKeditor in FF3 from local filesystem
// without security.fileuri.strict_origin_policy disabled.
if ( document.location.protocol == 'file:' )
{
   try
   {
      window.parent.document.domain ;
   }
   catch ( e )
   {
      window.addEventListener( 'load', function()
         {
            document.body.innerHTML = '\
               <div style="border: 1px red solid; font-family: arial; font-size: 12px; color: red; padding:10px;">\
                  <p>\
                     <b>Your browser security settings don\'t allow FCKeditor to be opened from\
                     the local filesystem.<\/b>\
                  <\/p>\
                  <p>\
                     Please open the <b>about:config<\/b> page and disable the\
                     &quot;security.fileuri.strict_origin_policy&quot; option; then load this page again.\
                  <\/p>\
                  <p>\
                     Check our <a href="http://docs.fckeditor.net/FCKeditor_2.x/Developers_Guide/FAQ#ff3perms">FAQ<\/a>\
                     for more information.\
                  <\/p>\
               <\/div>' ;
         }, false ) ;
   }
}

It's easy to trigger that warning in Firefox 3 loading the _samples folder. If your code has a different structure it might be OK for Firefox, but you can't expect us to guess how to fix your problems in IE just but reading your posts.