Fixing TinyMCE Unsaved-Changes Warnings in Evolution CMS

Editor trust drops quickly when the backend stops warning about unsaved changes. the article documented a long-standing TinyMCE integration bug where the dirty-state handler was wired incorrectly for some configurations.

The key fix

In the old TinyMCE integration, this logic:

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

needed to become:

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

Follow-up improvement

The donor also refined the handler so submitting the form would not trigger a false warning:

var runHandler = true;
document.mutate.addEvent('submit', function(){ runHandler = false; });
function myCustomOnChangeHandler() {
    if (runHandler) { documentDirty = true; }
}