Support Forum Support JCE Editor Firefox 9.0.1 JCE 2.0.19
Message
  • A subscription is required to to post in this forum - Subscribe

Firefox 9.0.1 JCE 2.0.19

Link to this post 12 Jan

Firefox has just automatically updated to 9.0.1 and now when text is displayed in the editor it flashes and then disappears and the editor is blank. I have checked with IE 8 and also earlier versions of FF and the editor is working correctly. I have another user who has the same problem on a different site. So this is a bug of some description. Joomla 1.5.25. I have also managed to replicate on two different 1.5 sites. The same problem exists with JCE 1.5.11 so I think this is a FF issue.

Can someone check and confirm.

Regards
Paul

Link to this post 13 Jan

Same here.. When i open an arcticle the JCE editor is loading and loading. Sometimes i have to stop the page and exit it and do it all over again. It is very time consuming and nerve wrecking.

Can you tell us how to fix this or what exactly is causing this?

Link to this post 13 Jan

I have tested FF 9.0.1 and JCE 2.0.19 and don't get any error message but am unable to click into the editor - this is affecting the textarea with another component only (RSEvents) rather than the article editor so it appears to be down to individual implementation as well.

I've tested in FF9.0.1 and JCE Component Version 1.5.7 / Plugin Version 1.5.6 and that shows the following error, again the article editor is fine, it appears to be the implementation with other components that's having a problem:

Error: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIDOMHTMLDocument.implementation]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: http://{siteURL}/plugins/editors/jce/tiny_mce/tiny_mce.js?version=156 :: <TOP_LEVEL> :: line 1" data: no]

Link to this post 13 Jan

I had a similar problem with iProperty and enabling the System - Mootools Upgrade did it for me as temporary fix.

Link to this post 13 Jan

I agree enabling mootools fixes the issus. Is this likely to cuase any issues with other components modules ?

Link to this post 13 Jan

but make sure it does not break things on the front end. It was in my case.

Link to this post 13 Jan

Replace editor.js in components/com_jce/editor/libraries/js/ with the file in the attached zip and clear your browser cache.

  1. editor.js.zip
Link to this post 13 Jan

Thanks. To clarify which versions of JCE is this file for v2 and v1.5 ?

Link to this post 13 Jan

JCE 2.0.19

Link to this post 14 Jan

just to confirm that it fixes the problem.

thanks a lot!

Link to this post 14 Jan

Ryan

I was about the report a different firefox 9.0.1 bug. This is that if joomla panes are loaded (they don't have to be used even) then editor content changes are ignored.

Your changed editor.js file fixes this problem too.

BUT - and this is a big but.

It appears as though editor content changes are ignored when joomla tooltips or modal popups are enabled. So the problem is not completely solved.


Geraaint

Link to this post 14 Jan

On closer inspection the problem appears to be related to which domready events are fired first.

If I just open a page with a 'problematic' editor on it by clicking a link to it then the scripts are loaded from the browser cache and I have a problem. But if I clear the browser cache or do a forced reload then sometimes the problem doesn't manifest itself and everything is ok.

Link to this post 14 Jan

Another attempt at a fix - this uses a domready type event to load the editor (as before) but delays the loading by 1 second, allowing other scripts to execute first (like tabs etc.)

Replace editor.js in components/com_jce/editor/libraries/js/ with the file in the attached zip and clear your browser cache.

  1. editor.js.zip
Link to this post 14 Jan

I now just get the 'hide/show' text appearing and this doesn't respond to a mouse click.

No javascript errors just that

tinyMCE.execCommand('mceAddEditor',0,el.id);

does nothing.

Link to this post 15 Jan

I now just get the 'hide/show' text appearing and this doesn't respond to a mouse click.

No javascript errors just that

tinyMCE.execCommand('mceAddEditor',0,el.id);

does nothing.

This is caused by the "fixTabbedWebkit" function in JEvents - yours is executing before JCE has been initialised which causes tinymce to attempt to load the "simple" theme, which doesn't exist in JCE.

Link to this post 15 Jan

I have adjusted JCE to load after a 50ms delay rather than 1000 as in the previous file. This should work OK now with JEvents.

Replace editor.js in components/com_jce/editor/libraries/js/ with the file in the attached zip and clear your browser cache.

  1. editor.js.zip
Link to this post 15 Jan

Hi Ryan

With a timeout of 50 milliseconds AND removing all references to tabs in the edit page (keeping the joomla modal and tooltips libraries loading) in Jooml a 1.5 with mootools upgrade enabled then this is what happens in firefox 9.0.1.

Edit event (with scripts in browser cache) - editor loads but show/hide button is unresponsive and content of editor is ignored when clicking save.

Edit event (with scripts NOT from browser cache e.g. ctl-r) editor loads and the show/hide button works and the editor content IS saved.

If I disable the modal and tooltips behaviours in Joomla then everything is ok. So the problem is definitely interaction with the Joomla modal, tooltips and tabs libraries where the problem arises.

I had an old version of JCE on a Joomla 1.7 site (v. 207) with no problems TinyMCE. I then upgraded this to 2.0.19 (unmodified i.e. without the editor.js fix) and the problem then started in Firefox - so the issue is not just relating to MooTools 1.2.5. and seems to have started between version 2.0.7 amd 2.0.19.

Geraint

Link to this post 16 Jan

Thank you for the hints & tips + the download which sorted it.

Link to this post 16 Jan

Ok, here is I hope the final attempt at fixing this issue.

Here the editor is loaded using the window.onload method instead of "domready" as before. The difference is that window.onload is fired when the entire page has loaded (including images etc.) and therefore should guarantee that other scripts (tabs, tips, modal etc.) have executed already. As a fallback to prevent situations where a large image or some other asset would prevent the window.onload event from executing quickly, a "domready" event is set to fire 1000ms after the dom is ready - in most cases window.onload will fire first.

I have tested this on a live site with JEvents 2.0.11, Virtuemart 1.1.9 and RedShop 1.1.9.4 - all extensions that load the editor in tabs and have had reported problems - with both a clean cache and with cached scripts.

Replace editor.js in components/com_jce/editor/libraries/js/ with the file in the attached zip and clear your browser cache.

  1. editor.js.zip
Link to this post 16 Jan

I can confirm this solves the problem in Joomla 1.7.3 and in Joomla 1.5.25 with the MooTools upgrade plugin NOT enabled.

I still see the problem in Joomla 1.5.25 when the MooTools upgrade plugin IS enabled.

Search

Tweets

JCE

JCE has won the J!OSCAR for best Free Joomla! Add-on! A big thank you to everyone who nominated and voted for us! #jce #jab12

by JCE




We will need to set cookies to do this - Learn More