editor-style.css file is empty, doesn't get updated

The latest version of the plugin does not check the _POST indices before testing them, and each style field with undefined index will throw errors.

It is possible to modify the original PHP file to resolve the issue.

In tinymce-advanced-professional-formats-and-styles.php make the following changes:

Near line 219 (before the bb_taps_backend_page(), add:

function undef_post_check($post_index) {
	if(isset($_POST[$post_index])) {
		return $_POST[$post_index];
	} else {
		return "";
	}
}

Then replace a number of _POST[] references with calls to the undef_post_check() function – near 250 (after pasting the above):

// WordPress sometimes tries to escape the HTML when saving something to wp-options
		        for($i=1;$i<=$all;$i++) {
		        	$allowed=true;
					$field0 = undef_post_check("addstyledrop_0_".$i);
		        	$field1 = undef_post_check("addstyledrop_1_".$i);
					$field3 = undef_post_check("addstyledrop_3_".$i);
					$field4 = undef_post_check("addstyledrop_4_".$i);
					$field7 = intval(undef_post_check("addstyledrop_7_".$i));
					$field8 = intval(undef_post_check("addstyledrop_8_".$i));

And also near 283:

if(undef_post_check('addstyledrop_5_'.$i.'_'.$a.'_key')!="" && $_POST['addstyledrop_5_'.$i.'_'.$a.'_val']!="") {

And near 294:

if(undef_post_check('addstyledrop_6_'.$i.'_'.$a.'_key')!="" && $_POST['addstyledrop_6_'.$i.'_'.$a.'_val']!="") {

Thanks! I will try that.

When I implemented this I added an extra column that could be used to order the rows. If you are interested in that I can tell you how to add it. It is not difficult, and it allows you to have more control over the order that the items appear in when they are in the tinymce styles dropdown.

Also, you may notice the the ‘Delete Row’ anchor does not work. It is not possible to hide an element using a child of that element. It does not matter – you just need to clear the name of a style you create and when you save the settings the row will be deleted.

I am not sure if this plugin is still in development. There are a handful of plugins that I use on a regular basis that have been orhphaned. I will probably end up releasing “+” versions of the originals with bugfixes and updates.