@helga:
I had the same issue using the multisite setup, but seem to have found a temporary workaround using the single-site setup version of the Montezuma theme (which, as you suggest, performed the dual-color span tag input correctly). I'm no 'code poet' or anything, but here's what I did:
I backed up then replaced
wp-content/themes/montezuma/admin/default-templates/javascript/javascript.js, and the default CSS file
wp-content/themes/montezuma/admin/default-templates/css/grids/resp12-px-m0px.css with the code from
style.css and
javascript.js found in the single-installation
wp-content/uploads/montezuma folder.
For me, it appeared to involve being able to write a
montezuma theme folder to
wp-content/uploads/ - despite already having the necessary permission to do so. See, e.g., starting at line 22 of
wp-content/themes/montezuma/functions.php, which looks something like this:
Code:
21 /*************************************************************************
22 Default CSS served INLINE because wp-content/uploads is not writable.
23 This will change once wp-content/uploads is writable
24 **************************************************************************/
25 ';
26 $bfa_css .= implode( '', file( get_template_directory() . "/admin/default-templates/css/grids/resp12-px-m0px.css" ) );
27 foreach ( glob( get_template_directory() . "/admin/default-templates/css/*.css") as $filename) {
28 $bfa_css .= implode( '', file( $filename ) );
29 }
30 $bfa_css = str_replace( '%tpldir%', get_template_directory_uri(), $bfa_css );
31 $bfa_css = "\n<style type='text/css'>\n" . $bfa_css . "</style>\n";
32 }
And so, for whatever reason, since the theme is not able to write to
wp-content/uploads, it uses the CSS and JS from
admin/default-templates/. I wonder if it is the Montezuma theme lacking write permissions, or if it has something to do with setting site/theme permissions from the WP "Network Admin" backend?
In any case, hope this helps.