We are having an issue where WYGWAM fields are disappearing on initialization of the js in the Edit Entry screen in the control panel. This is only for IE8 and IE9; other browsers work fine. This behavior is consistent whether we let the fields initialize on load or if we initialize on focus (in which case, the field's content loads and is visible, but disappears on click).
The channel contains a series of Matrix fields, including WYGWAM, Assets, and Playa fields. We are running an install of EE2.5.5, Matrix 2.5.3, Playa 4.3.3, and Assets 2.0.5.
In the browser console, we are seeing the following two errors:
- Not enough storage to complete this operation. ckeditor.js, Line 13
- Object doesn't support this property or method. compressed.js; Code: 0; Line 39.
Note, turning off nsm_morphine_theme where the compressed.js code resides eliminates the second js error, but does not resolve the issue above.
Here is a screen shot per Lisa Wess' request below. It is the Text field which has the Wygwam field type; the other empty fields simply do not have data entered in them.
------------------------------- UPDATE -------------------------------
There are two issues, both of which appear to be related to upgrading to Assets 2.
First, on upgrading we have the same issue as this: Clicking on folders in the Assets 2 file manager does not work on IE8.
Applying the hack Kevin Lees suggests takes care of the issue where the Assets 2 dialog box will not allow the user to select items from the popup.
The second, original issue -- that the Wygwam fields are not instantiating -- appears to be related to the control panel page making over 31 CSS calls; IE8/9 have a hard limit of 31 CSS calls, ignoring any calls above that number.
I believe this behavior is related to a change in Assets 2, which introduced a number of small, separate style calls in the head. No bid deal, except IE8/9 is counting each against the total. Therefore a page with multiple matrix and assets fields pushes past the 31-call limit.
Short of downgrading to Assets 1, the only fix we've found is to force the user to use Compatibility mode, which doesn't impose the 31-call limit.
I would be curious to hear if anyone else is having this problem or has found a better, long-term solution.