Conflict with Gantry Template

Hi Justin,
after a difficult debug session I found that the problem is caused by a conflict between MooTools (included in Gantry framework) and the QuickTags text editor (included in WordPress core).
The Black Studio TinyMCE Widget javascript code sits in between the two, but can’t do anything to prevent the issue (at least not in a easy way). The problem is that MooTools “pollutes” javascript Arrays with custom prototype properties, which are not handled correctly by the QuickTags initialization code. The problem is not restricted to this case, but it’s a general MooTools issue. You may find further info in this discussion.

A quick fix would involve the modification of a WordPress core file, which is however not recommended (you’d lose modifications after every WP update).

Anyway, here’s how to fix. First, enable SCRIPT_DEBUG, which forces WordPress to use not minified javascript files, by adding the following in your wp-config.php:

define('SCRIPT_DEBUG', true);

Then open the file wp-includes/js/quicktags.js and locate the following snippet (around line 249):

for ( inst in t.instances ) {
			if ( '0' === inst ) {
				continue;
			}

and change it to:

for ( inst in t.instances ) {
			if ( '0' === inst ) {
				continue;
			}
			if (! t.hasOwnProperty( inst )) {
				continue;
			}

Alternatively, you may not enable SCRIPT_DEBUG and change the minified version of the file (quicktags.min.js).

I may try to report this to WordPress core bug tracker, but I’m not sure they would apply the above change.