Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The body edit fields from the node/add form are blank when used with Internet Explorer 7 and IE8 / WinXP.
I get the same error message from my DebugBar:
Line 11 - Error Insufficient memory to continue this operation.
In IE8 debugger tool, i get the following errors:
'Drupal' is undefined on line 21, 25 and 28 in ckeditor.config.js
And the same error 'insufficient memory' on line 11 in ckeditor.js
No problem in Google Chrome, nor in FF3.5.
Any workaround? Hints?
Comment | File | Size | Author |
---|---|---|---|
#13 | ln12_error.png | 8.33 KB | rhimes |
#13 | ln19_error.png | 8.24 KB | rhimes |
#13 | ln129_error.png | 8.05 KB | rhimes |
#13 | ln3048_error.png | 8.27 KB | rhimes |
#13 | debug.png | 64.79 KB | rhimes |
Comments
Comment #1
mephir CreditAttribution: mephir commentedCan you write more about configuration of Drupal and CKEditor module.
Which version are you used, additional modules, ckeditor load method, because i can't confirm this bug, in lines 21, 25 and 28 isn't nothing connected with Drupal object, maybe you modified your ckeditor.config.js, if it is true, please attach it to post.
Comment #2
mathieu_ch CreditAttribution: mathieu_ch commentedHey, thanks for this fast reply! Cool!
I'll try to be exhaustive... But if there's anything missing, tell me.
BTW, the errors line 21 etc didn't appear again on further tests.
Thanks agains.
Mat
====================================
Drupal 6.14, themed with Blueprint CSS.
CKEditor Module is 6.x-1.0-beta1
CKEditor is version 3.1, taken here http://drupal.ckeditor.com/download/ckeditor_3.1_svn.zip .
No modified template disk is used for node/add/something pages.
There are no other editor installed on the site, some have been, but I removed them.
The content type is basic Page and an Article content-type w/ CCK Filefield, Scheduler, Nodetitle, etc. Nothing comes to my mind as interfering with that. All other Javascript seems to work as usual.
====================================
The complete error message from the DebugBar is:
====================================
Here's the error message I get when I try the "revert to the plain text editor" link.
====================================
The Default Profile settings I use are in the attached image.
====================================
Here's the config.js, it's unmodified.
====================================
Comment #3
wwalc CreditAttribution: wwalc commentedCan you check whether you have this bug on a IE7/IE8 without any add-ons (perhaps check on another computer)?
I'm just thinking that the problem might be in DebugBar + CKEditor or DebugBar + other module + CKEditor.
Could you also check do you have any problems in IE on the following web sites: http://ckeditor.com/demo and http://drupal.ckeditor.com/ (scroll down to the bottom to add a comment).
Comment #4
mathieu_ch CreditAttribution: mathieu_ch commentedI first noticed on IE 7 / WinXP and not the machine I was developping from. This test machine has no add-ons, no extras.
I then checked it on my IE 7 and 8 /WinXP, this machine is used for development, with IE Collection and IE Tester. I got the same errors on the two.
The screenshots attached to this reply are all taken from a 3rd computer, IE8 vanilla. CKEditor Demo site works fine. My site goes awry.
Could it be javascript overload? Could it be the theme I use?
Thanks for your help!
[edit: typos]
Comment #5
wwalc CreditAttribution: wwalc commentedCan you switch to Garland theme for a while to see whether that fixes the problem?
If that does not help, I suppose it might be a conflict with some module.
Last but not least, check whether using CKEditor with patch 4733, that is available here: http://drupal.org/node/652466 (see comment #5), changes anything.
Comment #6
mathieu_ch CreditAttribution: mathieu_ch commentedCKEditor under Garland theme works fine. So it's theme...
OK, I know you won't debug every theme of every themer around the globe, but where should I start looking in my theme to make CKEditor work in my custom Blueprint theme?
Comment #7
mephir CreditAttribution: mephir commentedWith blueprint theme i cannot reproduce this error, can you disable cusom javascript and look if it help ?
Comment #8
mathieu_ch CreditAttribution: mathieu_ch commentedI think I got it.
The Date Popup module (from the Date module) seems to be responsible for all that.
It was used in the node/add/*something* page with the Scheduler module.
The module is turned off and everything is fine in IE7 and IE 8 now.
Thanks for your time and help find a workaround.
Comment #9
mathieu_ch CreditAttribution: mathieu_ch commentedComment #10
jdelaune CreditAttribution: jdelaune commentedAlso getting that error, I'll check if it's down to the date module as well, what are you using instead now? Since the date module works fine without ckeditor.
Comment #11
jdelaune CreditAttribution: jdelaune commentedWasn't a date pop-up issue for me in the end. The new CKeditor 2.1 version fixed things for me.
Comment #12
mathieu_ch CreditAttribution: mathieu_ch commentedIn fact, it's not all the Date module that's a problem. It's only the Date Popup which is part of the Date module.
Well, for the site's contributors, it means they'll have to type the publish/unpublish date for the Scheduler module.
It's not that much of a problem for the site's use.
Comment #13
rhimes CreditAttribution: rhimes commentedWell actually.... NOT solved
upon seeing comments #8 & #12 I started to investigate Date/Date Popup, as I do have date fields on my content type - and after @ 1/2 hr of getting no where, suddenly dawned on me that my date fields aren't using the pop-up, but rather the select input - so looks like it may not have anything to do with Date at all.
But I'm also experiencing two different manifestations of the problem -
#1 - locally testing
D6.17, CKEditor-1.x-dev-6-18-10, CKEditor script 3.3.1 - using Garland (and tons of other modules)
IE (8.0.6001.18702 - only add-on enabled is Java) displays Java errors on lns #12 & #24 - and shows a totally blank area where CKEditor should be like comment #4.
#2 - @ drupal.ckeditor.com/
using IE, got ln errors #19, #129 & #3048, and CKEditor LOOKS like it's there but clicking in the textarea is unsuccessful and can't be used (see editor_dead img) - if I try switching to plain text editor, that's when I got the #19 & #129 errors, and it won't switch!
BTW - locally & drupal.ckeditor.com are fine in FF3.6.3 & Chrome5.0.375.70 - AND - ckeditor.com/demo is AOKAY in all 3 browsers!
also attaching all error msg scrnshts & debug scrnsht
Comment #14
rhimes CreditAttribution: rhimes commentedmore accurate title
hadn't noticed was a s/r'qst - really a bug
and a critical one considering IE8 visitors @ drupal.ckeditor.com can't post
Comment #15
rhimes CreditAttribution: rhimes commentedoops
Comment #16
fairflow CreditAttribution: fairflow commentedI've just run into this issue as well. Latest IE8, no add-ons. Same insufficient memory error messages as in previous comments. Site running Newsflash theme (modified). ckeditor works fine in IE8 with Garland.
any progress on this issue?
I'm sure this is naive, but the simplest explanation is that there is an overload of javascript and that subsequent reported errors are a consequence of that; is there any way to allocate more IE8 resources to javascript to test this hypothesis? Or is the debug message about lack of storage unreliable?
This is a deal-breaker for me so it looks like a revert to fckediting unless a fix is imminent....
Comment #17
fairflow CreditAttribution: fairflow commentedFolks, I've just realised that I'm using 6.x-1.1, not the dev version, and I'm seeing the same error. Perhaps most folks don't use IE8? Apologies, if I should give them, for adding a comment to an issue queue for the wrong version.
Comment #18
mephir CreditAttribution: mephir commented@fairflow: i saw only one bug related with ie and ckeditor it's fixed into cvs. So please download dev version and check if bug still exists. Also third part scripts can possibly be in conflict with ckeditor. Some modules rewrite onload event so it could be a problem. If you have some additional modules please write which one.
Comment #19
rhimes CreditAttribution: rhimes commented@mephir: this might be for 6.x-1.x-dev and 6.x-1.1
I know it applies to dev on my local installation, and if your running 6.x-1.1 @ drupal.ckeditor.com, it applies to it as well. - unless you ARE able to post at drupal.ckeditor.com using IE8 - 'cause I sure can't!
Have you tested at drupal.ckeditor.com using IE8 lately?
Comment #20
rhimes CreditAttribution: rhimes commentedUPDATE
You'll think I'm smokin' something - but I just visited drupal.ckeditor.com again with IE8 - and low and behold I now CAN use the editor. Don't know what's changed since last trying (yesterday), but page is now loading without javascript errors, can enter the ckeditor textare, can switch to plain text editor etc.
I swear that for the last few days I was unable to do any of the above with IE8 - Has anything changed?
Comment #21
jonsbri CreditAttribution: jonsbri commentedMay be to do with IE limit on number of stylesheets
See http://cksource.com/forums/viewtopic.php?f=6&t=17318
I switched on ‘Optimize CSS files’ (admin/settings/performance) - and resolved CKE problem - however there may be problems with the optimizing as not all styles were being applied.
Comment #22
rhimes CreditAttribution: rhimes commented@jonsbri - thanks, took your advise and enabled ‘Optimize CSS files’ - editor now loading as expected in IE8 on my local enviroment
haven't yet encountered side effects, will post if any arise
@mephir: do you have ‘Optimize CSS files’ enabled, or 'Optimize JavaScript files', @ drupal.ckeditor.com?
Comment #23
rhimes CreditAttribution: rhimes commentedbetter set differently
Comment #24
wwalc CreditAttribution: wwalc commented@rhimes regarding drupal.ckeditor.com - we were using a custom module @ drupal.ckeditor.com that broke our demo web site in IE. Thanks for reporting the problem.
I'm testing the module locally using the latest stable release of Drupal (6.17) and a fresh dev copy of CKEditor module (2010-Jun-18) with CKEditor 3.3.1 and I do not have any errors in IE8.
It looks like large number of CSS files to be used in the editor might be a problem.
Comment #25
pat_bee CreditAttribution: pat_bee commentedHope this helps, what fixed this after upgrade for me was going into
Admin / Settings / CKEditor / Global Settings / Advanced Settings
the changing "Path to CKEditor" to just %m
that made it reappear but oddly enough when I went back to check that setting it had reverted back to
%m/ckeditor
Can't say I know why this worked but it did for me.
Comment #26
wwalc CreditAttribution: wwalc commentedComment #27
Foonaka CreditAttribution: Foonaka commentedThe IE stylesheet limit also was the cause of my issue. I turned on Optimized CSS under 'Site Configuration' --> 'Performance' and that did the trick for me.
Comment #28
aufumy CreditAttribution: aufumy commentedI had theme registry being rebuilt every page load.
I turned that off, and it seemed to help.
Also
http://drupal.org/project/ie_css_optimizer allows more options in terms of optimizing the css.
Comment #29
Compel CreditAttribution: Compel commentedThis is not to re-open the issue but to remind people to check their themes. CKEditor will not work in some themes unless CSS Optimizer is enabled. I was finally able to get it to display in Acquia Marina after enabling CSS Optimizer. This is because of a limitation built into IE that restricts the number of stylesheets that can be used. And more complex themes like Marina use more than that.
Comment #30
Garry Egan CreditAttribution: Garry Egan commentedThis issue is absolutely reproducable in IE9.
Go to http://ckeditor.com/demo using IE9 and clear out their sample text completely so nothing is inside the edit box. Click SOURCE to make sure it's all cleared out.
Now click SOURCE again to start editing. It will not let you type anything in the edit area.
I fired off a support email to CKSource but, suffice it to say, CKEditor for Drupal IE9 is NOT USABLE at this time.
I'll update this thread when i hear back.
Comment #32
Ela CreditAttribution: Ela commentedsubscribing
Comment #33
armyofda12mnkeys CreditAttribution: armyofda12mnkeys commentedsame issue as GarryEgan, .... I goto my page node in IE8 as drupal root user and hit Edit, and then click Source and it doesnt allow to edit source(regular non-source is interestingly allowed). Only allows Source editing it if you click Maximize button for some reason. Only affects IE, FF works fine as that user. Using Acquia Marina theme and turned on CSS optimization in Performance to no avail.
Comment #34
xbery CreditAttribution: xbery commentedThis issue is still a big problem but the solution mentioned in comment #24 worked like a charm! Thanks guys once more I am in your debth :-).
Lukas
Comment #35
guignonv CreditAttribution: guignonv commentedLike xbery...
I switched on "Optimize CSS files" in "admin/settings/performance" and it solved the problem on my site and IE8.
Comment #36
xbery CreditAttribution: xbery commentedWorked for me too! I did not find anywhere what the file (css, js) count limit is but this is the trick! It depends on the order of your theme js and css files and if it reaches 10-15 next will be stripped by IE. This results to missing files, errors and finally blank editor :-)
This saved my soul - i was going to rip my hair before finding solution this simple.
Comment #38
mkesicki CreditAttribution: mkesicki commentedHi,
@keke302 please write what problem do you have in english. Please don't open closed issues. If you have this problem please open new issue for it.
Comment #40
mkesicki CreditAttribution: mkesicki commented@keke302 as I sad please open new ticket for your issue and don't open closed tickets. In new issue add some description what problem do you have.
Comment #41
husumiao-1 CreditAttribution: husumiao-1 commentedThank you so much.
you give me so big hands.
Comment #42
lagassss CreditAttribution: lagassss commentedI have the same problem and I can't activate "Optimize CSS files" because I run Open atrium over drupal and file downloading needs to remain private.
Any other idea ?
Comment #43
-Mania- CreditAttribution: -Mania- commented@lagassss: you could try an alternative module such as http://drupal.org/project/advagg which works on private file system as well.
Comment #44
gleenk CreditAttribution: gleenk commentedFor me it works enabling css compression!
admin/settings/performance/
Optimize CSS Files -> Activate