IE 9 Javascript Issues: Failsafe Release of Foliopress WYSIWYG

Dear Foliopress WYSIWYG users,

Thank you to everyone who reported the issues with our editor not working properly in IE 9.0. After doing some testing we found that there are some  issues. The issues are related to FCKEditor which is the core editor. The same issues affect CKeditor (a newer version as well).

Here is the error message from debugging console when the post is being saved:

"Not enough storage is available to complete this operation."

The post is saved, but the editor stops working. Other messages appears when using the Link dialog:

SCRIPT65535: Invalid calling object
fckdialog.html, line 778 character 4
SCRIPT65535: Invalid calling object
fckdialog.html, line 111 character 4
SCRIPT65535: Invalid calling object
fckeditor.html?InstanceName=content&Toolbar=Basic, line 233 character 4

Other issues relates to the WordPress Linking Dialog which we added into the last version. It has issues for some users, so we've disabled it by default. Go to Settings -> Foliopress WYSIWYG -> Advanced -> Use WordPress Linking Dialog to re-enable it. There have been issues with the our original javascript linking pop-in as well.

For now, what we've done are:

  1. to disable Foliopress WYSIWYG in IE 9 offering a bare html version and a visible warning.
  2. to recommend Safari, Firefox 3+, Chromium (Chrome is spyware but works) or IE 7/8 instead.
  3. we've also made the WordPress linking dialogue optional and made our original javascript version default

We will keep working on an IE 9 version as people gradually solve the IE 9 security and javascript issues. For now, please use another browser.

If you are having any of these issues, upgrade to the new version now!

More information

This entry was posted in WordPress. Bookmark the permalink.

2 Responses to IE 9 Javascript Issues: Failsafe Release of Foliopress WYSIWYG

  1. sandip

    Hi, I am also facing issue with IE9 while using fckeditor. Do you have any update for this?

  2. Hello sandip,

    we are currently testing the new version of our editor with this issues fixed. We still miss some of our functions, but we are getting close.

    Thanks,
    Martin

Leave a Reply