There are several issues relating to an IE bug with CKEditor where the editor fails to appear but manages to still replace the default textarea with nothing: a broken situation where end users cannot type into the field. What resolved the issue for me was to Optimize CSS files (admin/settings/performance). I am using a Zen subtheme which comes packed with several more css files.

To reproduce:
- under drupal admin, ensure Optimize CSS files is not checked
- load a page with the editor in IE, see that it's broken as described
- under drupal admin, check Optimize CSS files
- reload the same test page-- CKEditor should appear

Optimize JavaScript files setting didn't do it for me.

While this solution worked for me, I am just posting this issue here for anyone experiencing the IE6 IE7 IE8 error message:

    Webpage error details
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
    Timestamp: Fri, 4 Jun 2010 15:33:38 UTC

    Message: Exception thrown and not caught
    Line: 23
    Char: 1835
    Code: 0
    URI: http://example.com/sites/all/libraries/ckeditor/ckeditor.js?l

    Message: Not enough storage is available to complete this operation.
    Line: 12
    Char: 657
    Code: 0
    URI: http://example.com/sites/all/libraries/ckeditor/ckeditor.js?l

I posted this issue as Needs Review in case the maintainer wants to try to tackle some "IE css issue detection and disable attempting to swap out for CKEditor" fix. I suspect, however, that such a mechanism should be a step before CKEditor module proper and actually come from core or another contrib module.

Comments

wwalc’s picture

Component: Code » Documentation
Assigned: Unassigned » wwalc
Category: bug » task

Let's add it to troubleshooting.

Ecio’s picture

I'm experiencing the same problem, unfortunately I cant enable "Optimize CSS files" because my download method is set to private (im using drupal for an intranet project and i need to protect attachments). How can I solve this problem? Im currently trying other wysiwyg editors (also via wysiwyg module) but it looks like some problems always arise on IE7/IE8 due to css/js handling.

Benj’s picture

Drupal 6.17
CKeditor 1.0
Advanced Forum 1.1
Zen 1.1

Similar problem here. CKeditor was rendering but when bringing up the image dialog box, it rendered unusable. Smiley dialog box was usable but its formatting was messed up. I get the error: Not enough storage available to complete this action. ckeditor.jsI, line 12 character 383.

This only accrued when using CKeditor in the forum (advanced forum module) and when using Zen theme or Zen sub-theme with css optimize off. I use CKeditor elsewhere on the site, in a simple content type, and there it works correctly using Zen theme and css optimize off.

Also, I tried the Garland theme, and CKeditor worked correctly in all instances.

Ecio’s picture

Actually I had this problem with Garland too. I've partially solved by using IE Unlimited Css (i had "Not enough storage" message because of more than 31 CSS in modules/themes) and using ckeditor instead of jwysiwyg as editor via wysiwyg API (using jwysiwyg i got a "Object doesn't support this property or method" error). Of course these are not the best solutions but i cant upgrade to D7 in order to have CSS optimization with private download method.

_snake_’s picture

Hi,

I have the same problem...

In Firefox the ckeditor fields are showed without problem (with and without Optimize CSS files activated), but in IE7 and 8 are showed if the content type is a node with only the title and the body.
If the content type has more fields, the CKEditor is not showed...
Activating the option "Optimize CSS files" the CKEditor appears! So thanks texas_bronius for the post!
I hope that Issue will be solved in the next release

Regards

agileware’s picture

Same problem, solution in my case was to change the Drupal performance options as follows:
Optimize CSS files: enabled
Optimize JavaScript files: disabled

Error occurred using:
MS Internet Explorer 8

With the following Drupal modules:
Wysiwyg 6.x-2.1
IMCE Wysiwyg API bridge 6.x-1.1
IMCE 6.x-1.4

palmaross’s picture

I had this problem with TinyMCE... No matter which editor you use - it's the problem of IE, but not the editor.
Really issue is that IE "dosn't see" css file of your editor. The editor's css file, which "draws" editor's textarea and toolbar.
There may be two reasons. First - IE "bug", called "31 css file" (IE can load only 31 file CSS), so when Optimize CSS enabled, your editor can load and link its own CSS file in IE.

So the first solution may be: force IE to load more than 31 css files. For example, by using module IE Unlimited CSS Loader. Or, if your theme settings have checkbox "Don't limit css files for IE" - enable this checkbox.

But this solution does not work always. (In my case, it did not work). So I force IE to load editor's css file through its own stylesheet (if your page.tpl.php has a lines:

<!--[if IE 8]>
  <?php print $ie8_styles; ?>
  <![endif]-->
  <!--[if IE 7]>
  <?php print $ie7_styles; ?>
  <![endif]-->
  <!--[if lte IE 6]>
  <?php print $ie6_styles; ?>
  <![endif]-->

then you can find files ie8-fixes.css and ie7-fixes.css in your theme /css folder).

1. Find needed editor's css file (eg, with firebug click any button in editor toolbar and see - wich css file in using). For example, for TinyMCE this one is ui.css
2. In the begin of ie8-fixes.css (and ie7-fixes.css) write: @import "filepath_to_css_file" all;. filepath should be relative path! Eg:
@import "../../../../libraries/tinymce/jscripts/tiny_mce/themes/advanced/skins/default/ui.css" all;

That's all. Now you can see your editor... with Optimize CSS disabled.

And sorry my bad english!

dczepierga’s picture

Status: Needs review » Closed (fixed)
yesct’s picture

Optimize CSS didn't help my case. The conditional IE css includes did. But instead of @import,

<link rel="stylesheet" href="style1.css" type="text/css" media="all" />

as I read a bit of: http://john.albin.net/css/ie-stylesheets-not-loading