This started out as me trying to sort out the code display, which
incidently, I still haven't managed to do and ended up as a plugin to
help manage TinyMCE settings.
I've been tweaking and messing with the layout.cfm file trying to sort out how to get the code panels working properly without having mess about with switching off javascript and tinymce and so on.
I get kinda grumpy when I start messing with core files, so I decided I should really work out how to make the changes more flexible and easier to fix when updates to MangoBlog are released.
This is by no means a silver bullet. If the admin/layout.cfm file is changed it will be necessary to remake the layout.cfm file for the plugin. Hopefully someone will find it useful
What I've done is taken a copy of the standard layout.cfm file and pulled out the plugin, button bars and extended valid element setting sections. These I've replaced them with 3 admin events that are associated with the a matching set of preferences. I've also added in an admin event and preference so that you can add any additional config that you might need for specialist plugins. For instance this could be used for the plugin_asffileexplorer_browseurl and plugin_asffileexplorer_assetsUrl settings.
That's about it really.
Couple of things to know:
The settings page is kinda ropey, as I haven't really looked into the CSS side things properly. If anyone fancies tidyig it up..... :D
When you activate the plugin it will take a copy of your existing layout.cfm file and replace it with one from the plugin with the admin events in it.
You can download the plugin here
Please have a play with it, let me know of any enhancements you'd like to see and problems you find. And please for love of all that's good someone sort out my shocking CSS in the settings form! ;)
Phase 2 : sort out a plugin to implement SyntaxHighlighter with the ColdFusion brush and the syntaxhl tinymce plugin.