We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 31178
    • 128 Posts
    I know in previous versions there have been a few problems with ’navigate away’ when making changes to a TinyMCE field, particularly with IE7.

    In the current version it seems there is no ’Are you sure you want to navigate away from this page?’ implementation at all when a change has been made? Tested in FF3, IE7 (with fixes to get it working) and IE8.

    BTW - The whole ’documentdirty’ implementation does not work with Chrome browsers at all, TinyMCE field or otherwise... with this or previous MODx releases.
      • 33014 ☆ A M B ☆
      • 1,231 Posts
      Quote from: uxello at Apr 12, 2010, 02:54 AM

      BTW - The whole ’documentdirty’ implementation does not work with Chrome browsers at all, TinyMCE field or otherwise... with this or previous MODx releases.
      It can be settled in "autosave" tinymce-plugin.
      http://wiki.moxiecode.com/index.php/TinyMCE:Plugins/autosave
        • 31178
        • 128 Posts
        Thanks yama. I tried it... should just need to add ’autosave’ to the ’Web Plugins’ list on the TinyMCE plugin config??, but it did not seem to do anything.

        Also for Chrome browser it is not just the TinyMCE field that does not pick up document change, it is any field on the resource.
          • 31178
          • 128 Posts
          Quote from: yama at Apr 12, 2010, 02:59 AM

          Quote from: uxello at Apr 12, 2010, 02:54 AM

          BTW - The whole ’documentdirty’ implementation does not work with Chrome browsers at all, TinyMCE field or otherwise... with this or previous MODx releases.
          It can be settled in "autosave" tinymce-plugin.
          http://wiki.moxiecode.com/index.php/TinyMCE:Plugins/autosave


          Just been looking into this further and I think there is an incorrect logic in tinymce.functions.php line 180

          $ph['onchange_callback']       = ($params['frontend']!==false)? "'myCustomOnChangeHandler'" : 'false';


          I think this should be

          $ph['onchange_callback']       = ($params['frontend']==false)? "'myCustomOnChangeHandler'" : 'false';


          so document dirty is triggered for backend manager editing? This would mean autosave would not need to be used