this morning I have upgraded Firefox to version 11. If I have more than one TinyMCE in one document type, I can edit only one of the two or tree TinyMCE's in this node in content section? I have found this bug in all of my 4.7.1 umbraco-websites. Has anyone an idea to resolve this bug?
Does anyone have some good upgrade instructions for TinyMCE. There are some implementation notes in a text file under umbraco_client\tinymce3, but they aren't detailed enough for me to figure out how to modify TinyMCE 3.5b2 to work in Umbraco 4.7.1.1.
We're aware that Firefox 11 breaks RTE functionality in v4.7.x. The problem is a bug in FF - not Umbraco. Bug is fixed in latest FF nightly!
I’m not sure when Firefox is going to officially release the fix, but if you if you have a problem with FF in Umbraco and don’t want to wait, then you can download the latest nightly build for Firefox here:
But but but... unless I miss something obvious, the upgrade proposed by Hardi just overrides the "umbraco" TinyMCE with the "standard" TinyMCE, so obviously it MUST break quite a lot of things! Not the right way to do it!
A temporary fix I found for those who don't have the ability to upgrade all their users to the nightly build as is my case, you can edit the file under ~/umbraco/editContent.aspx. Then add the following inside the jQuery(function() { });
As a side note, it wasn't just Umbraco's TinyMCE that was affected by this Firefox bug, but on some other sites of ours using an older FCKEditor (v2) (a different kind of WYSIWYG editor) we noticed that on a page with multiple editors, only the first one would appear. (Although interestingly, we didn't have any problems with the v3 CKEditor.)
TinyMCE Bug in Firefox 11
Hello,
this morning I have upgraded Firefox to version 11. If I have more than one TinyMCE in one document type, I can edit only one of the two or tree TinyMCE's in this node in content section? I have found this bug in all of my 4.7.1 umbraco-websites. Has anyone an idea to resolve this bug?
Regards,
Sören
Same issue here, doh! Wonder if it's time to look into upgrading TinyMCE?
Work-in-progress, see http://our.umbraco.org/forum/core/general/29859-TinyMCE-version
Don't know if it will succeed, though.
I'm also getting this problem. Is it a TinyMCE issue and not a bug with FF.
I was very suprised be viewing such problem.
First thought was to charge mode elements or even editor_selector, but didn't work.
So i've solve this problem by upgrating TinyMCE to the newest version, such is 3.5b2
It worked for me.
To upgrade TinyMCE, follow this instruction
http://fynydd.com/kb/updating-tinymce-in-umbraco/
Point 2 should read .....navigate to jscripts\tiny_mce\
EDIT: You're right Jennifer! It broke page selector, do not upgrade!! :((
I upgraded TinyMCE to 3.5b2 using the instructions above, but now I cannot select a link from the Content Tree.
Didn't do this on a production server did you?
No, of course not, I always try things out in a test environment first.
Does anyone have some good upgrade instructions for TinyMCE. There are some implementation notes in a text file under umbraco_client\tinymce3, but they aren't detailed enough for me to figure out how to modify TinyMCE 3.5b2 to work in Umbraco 4.7.1.1.
Niels Hartvig @ umbraco
We're aware that Firefox 11 breaks RTE functionality in v4.7.x. The problem is a bug in FF - not Umbraco. Bug is fixed in latest FF nightly!
I’m not sure when Firefox is going to officially release the fix, but if you if you have a problem with FF in Umbraco and don’t want to wait, then you can download the latest nightly build for Firefox here:
http://nightly.mozilla.org/
But but but... unless I miss something obvious, the upgrade proposed by Hardi just overrides the "umbraco" TinyMCE with the "standard" TinyMCE, so obviously it MUST break quite a lot of things! Not the right way to do it!
You are correct. To fix this particular problem you don't need to upgrade TinyMCE, as stated in my previous message the bug is actually with FireFox:
http://nightly.mozilla.org/
A temporary fix I found for those who don't have the ability to upgrade all their users to the nightly build as is my case, you can edit the file under ~/umbraco/editContent.aspx. Then add the following inside the jQuery(function() { });
jQuery(".header li").click(function(){
jQuery(".tabpagecontainer").find(".propertyItem table").delay(1000).height(jQuery(this).height() + 5);
});
This will fix it whenever they change to the tab that's broken or switch off and back on.
I can also confirm that the nightly build does fix this, however it's not released as a full version to general public yet so not easily available.
Had same bug today in EPI Server CMS 6 :(
http://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=57591&epslanguage=en
The just released update for Firefox (v.12) fixes this issue :-)
As a side note, it wasn't just Umbraco's TinyMCE that was affected by this Firefox bug, but on some other sites of ours using an older FCKEditor (v2) (a different kind of WYSIWYG editor) we noticed that on a page with multiple editors, only the first one would appear. (Although interestingly, we didn't have any problems with the v3 CKEditor.)
Glad that FF12 is out!
Confirmed that the latest firefox 12 fixes this
is working on a reply...