Was there a decision made about co-maintainers? I didn't follow that thread to its conclusion. I would be willing deal with the backlog in the issue/support queue until a decision can be made about the long term direction if it helps avoid bypassing the .js files. I think we can find a solutions that restore the 4.7 functionality without comprimising on long term compatibility with TinyMCE framework. I think if the hack I wrote last night can be flushed out as a patch that restores the GUI role based customization, that will go along way towards putting out this fire. Another thing that might help is a dojo-style video showing users how to customize their theme .js. I think I can get a someone to do that in the next day or 2. Hopefully that will give drupal-id a chance to share his thoughts. It may turn out that drupal-id isn't up to the task of maintaining the TinyMCE module and we have no option but to revert the the patched 4.7 version, but I'd like the discussion to be driven by the long term benefits of each direction rather than the short term issue of a large number of very vocal users who don't want to edit a comma separated lists. ___ Kevin Reynen Integrated Media Coordinator Reynolds School of Journalism and Advanced Media Research University of Nevada, Reno