Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Sören Deger 733 posts 2844 karma points c-trib
    Mar 15, 2012 @ 14:01
    Sören Deger
    1

    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

  • Tom Fulton 2030 posts 4998 karma points c-trib
    Mar 15, 2012 @ 14:42
    Tom Fulton
    0

    Same issue here, doh!  Wonder if it's time to look into upgrading TinyMCE?

  • Stephen 767 posts 2273 karma points c-trib
    Mar 16, 2012 @ 12:30
    Stephen
    0

    Work-in-progress, see http://our.umbraco.org/forum/core/general/29859-TinyMCE-version

    Don't know if it will succeed, though.

  • suzyb 474 posts 932 karma points
    Mar 19, 2012 @ 15:30
    suzyb
    0

    I'm also getting this problem.  Is it a TinyMCE issue and not a bug with FF.

  • mikeshema 1 post 21 karma points
    Mar 20, 2012 @ 17:31
    mikeshema
    0

    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.

  • Aximili 177 posts 278 karma points
    Mar 22, 2012 @ 06:10
    Aximili
    0

    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!! :((

  • Jennifer Killingsworth 191 posts 248 karma points
    Mar 22, 2012 @ 19:54
    Jennifer Killingsworth
    0

    I upgraded TinyMCE to 3.5b2 using the instructions above, but now I cannot select a link from the Content Tree.

  • David 57 posts 80 karma points
    Mar 22, 2012 @ 19:55
    David
    0

    Didn't do this on a production server did you?

  • Jennifer Killingsworth 191 posts 248 karma points
    Mar 22, 2012 @ 19:57
    Jennifer Killingsworth
    0

    No, of course not, I always try things out in a test environment first.

  • Jennifer Killingsworth 191 posts 248 karma points
    Mar 23, 2012 @ 13:46
    Jennifer Killingsworth
    1

    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.

  • Jennifer Killingsworth 191 posts 248 karma points
    Mar 26, 2012 @ 18:39
    Jennifer Killingsworth
    0

     

    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/

  • Stephen 767 posts 2273 karma points c-trib
    Mar 29, 2012 @ 11:06
    Stephen
    0

    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!

  • Jennifer Killingsworth 191 posts 248 karma points
    Mar 29, 2012 @ 14:18
    Jennifer Killingsworth
    0

    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/

  • FreedomChicken 12 posts 33 karma points
    Mar 30, 2012 @ 15:57
    FreedomChicken
    0

    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.

  • Simon steed 376 posts 688 karma points
    Apr 06, 2012 @ 12:28
    Simon steed
    0

    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.

  • Sjors Pals 617 posts 270 karma points
    Apr 13, 2012 @ 13:01
  • Stefan Kip 1614 posts 4131 karma points c-trib
    Apr 25, 2012 @ 11:20
    Stefan Kip
    1

    The just released update for Firefox (v.12) fixes this issue :-)

  • Funka! 398 posts 661 karma points
    Apr 26, 2012 @ 23:27
    Funka!
    0

    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!

  • Simon steed 376 posts 688 karma points
    Apr 27, 2012 @ 10:30
    Simon steed
    0

    Confirmed that the latest firefox 12 fixes this

Please Sign in or register to post replies

Write your reply to:

Draft