Hi Fusa,
it hasn’t been reported before.
Please can you try disabling your other plugins? I suspect one of them is including some CSS that is making the text white. If you find out which plugin is causing the problem please let me know so I can see if I can fix it from this end.
Regards,
Tom
Just noticed I have the same problem – visual editor Tiny MCE.
Btw, thanks Tom for all the responses and support and this awesome plugin.
Thanks, I see it’s with the Black Studio Tiny MCE widget.
It’s not easy to fix, it’s more than just the text showing as white (the buttons dont load for the editor either).
I’ll need to get in touch with the authors of that plugin to work out how to get it working properly with MMM.
Regards,
Tom
ok, thanks Tom. I did try deactivating plugins but to no avail.
I thought the “define(‘CONCATENATE_SCRIPTS’, false) statement did the trick but the fix only lasted for a minute which is odd.
Hi Fusa,
This is as far as I got:
[edit: wrong link, see below]
You can copy the code from the first post, just change ‘widgets.php’ to ‘nav-menus.php’.
That’ll get you so far (I think if you switch between the text and visual tab you’ll be able to see the text) but it wont fix it 100%.
I think it’s because MMM loads the panel contents with AJAX but the tinymce is expecting the widgets to be present on page load – thats the bit I need to fix (hopefully with the help of the developer as I am stumped!)
Edit: I see the author of that plugin has reached ‘support burnout’ and no longer appears to be responding to support threads.. I’ll have to see if theres another way to contact him.
Regards,
Tom
Hi Tom,
Am I pasting this code in my wp-config.php?
<?php
/**
* Requires Media Manager Plus >= 1.5
* Load MMP assets on widgets and customizer page to extend Black Studio Widget
*
* @param array $pages
* @return array
*/
function mmp_add_enqueue_pages( $pages ) {
$pages[] = ‘nav-menus.php’;
return $pages;
} // END
add_filter( ‘mmp_enqueue_pages’ , ‘mmp_add_enqueue_pages’ );
Thanks
John
Hi John,
Nope, put it at the bottom of your themes functions.php file. If the last line reads “?>” then paste it just above that, otherwise just paste it right at the bottom.
Here is the correct code:
function megamenu_blackstudio_tinymce( $pages ) {
$pages[] = 'nav-menus.php';
return $pages;
}
add_filter( 'black_studio_tinymce_enable_pages' , 'megamenu_blackstudio_tinymce' );
Regards,
Tom
Sorry, that code was wrong, I’ve edited my post with the correct code. But remember it won’t fix it fully so don’t expect miracles 🙂
Hi fusa,
Quick update on this, I think I see what’s going on now. I’ll need to spend a few hours on it but it should be fixed in the next release.
Regards,
Tom
Hi there,
I am the author of Black Studio TinyMCE Widget plugin. I am sorry for the delay but I’ve been pretty busy lately. As far as I can see, you managed to find a fix for the issue, based on a filter hook available in BSTW for that purpose. Please let me know if any change is needed on the Black Studio side.
Hi Marco,
Thanks for the response 🙂
The fix I posted above doesn’t really work too well. If I remember correctly the problem is because MMM loads the widget settings form using ajax, but Black Studio expects the html for the widget settings form to be there on page load. MMM also doesn’t fire the same jQuery events when widgets are added to the panel.
I did take a good look at this but I’ve forgotton exactly what I discovered – I’ll need to take another look and get back to you.
Regards,
Tom
Yes you’re going to have to seriously get that fixed. I know its a free plugin and both are amazing but it’s a pretty serious bug that will prevent many users from participating in either option.
Marco – not sure if you’re subscribed to this thread but I have found a fix.
After MMM loads the widget form (this happens after the ‘.widget-edit’ click event that Black Studio TinyMCE usally picks up on) I’m calling:
// Init Black Studio TinyMCE
if ( widget.is( '[id*=black-studio-tinymce]' ) ) {
bstw( widget ).deactivate().activate();
}
I realise I could also fire the ‘widget-updated’ event after the form loads, which would be picked up by your JS, but it seems a bit wrong to do that as the widget hasn’t actually been updated. Ideally I’d need something like a ‘widget-init’ or ‘widget-form-loaded’ event to call from this end (which does the same thing as ‘widget-updated’), but I think the above fix will do the trick 🙂
The fix will be in the next version.
Regards,
Tom
