Posted 10 months ago #
Getting the following error on the 'Widgets' screen after installing 3.2:
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'wp_tiny_mce_preload_dialogs' was given in /data04/c2630374/public_html/svoy/wp-includes/plugin.php on line 405
Established the wysiwyg plugin was causing the error.
Posted 10 months ago #
Hi Andy,
I've had contact with you trough e-mail. For others who are experiencing this problem, please leave a reply to this topic so I know it's not just Andy who is experiencing this bug!
Seems to be a BuddyPress issue, but it would be of great help if anyone could confirm this!
Danny
Posted 10 months ago #
I had a similar problem but realised it was an issue with the function.php file for my theme after fixing this the widgets area worked fine.
Posted 10 months ago #
Hi Danny,
I'm also having this problem in WordPress 3.2. I even tried turning off all other plugins and reverting to the WordPress Twenty Eleven theme.
So this problem seems to at least appear on a WordPress installation updated to version 3.2, with standard theme and no other plugins.
Hopefully it won't be too tricky to fix :)
Posted 10 months ago #
I have a work around for the moment. I added the following method to your "WYSIWYG_Widgets_Admin" class:
function preload_dialogs()
{
?>
<div id="preloaded-dialogs" style="display:none;">
<?php do_action('tiny_mce_preload_dialogs'); ?>
</div>
<?php
}And then replaced this line:
add_action('admin_print_footer_scripts', 'wp_tiny_mce_preload_dialogs');With this line:
add_action('admin_print_footer_scripts',array(&$this,'preload_dialogs'));It's probably not perfect, as I'm just working around the fact that the 'wp_tiny_mce_preload_dialogs' function can't seem to be called.
Maybe it'll help you work out the problem though, or give someone else a temporary fix :)
Posted 10 months ago #
Just committed a new version which should fix this problem.
Apparently wp_tiny_mce_preload_dialogs got renamed into wp_preload_dialogs and changed a bit. It is now already being called from wp_quicktags, which on his turn gets called from the_editor. What this means is that calling wp_tiny_mce_preload_dialogs is no longer explicitly necessary. :)
Japh, you definitely pointed me in the right direction. Thanks!
Now, it would be great if anyone could confirm that WYSIWYG Widgets 1.0.5 fixes this problem!
Posted 10 months ago #
Hi,
in my case TinyMCS doesn't show up, Never used that plugin before (now in WP 3.2)
Posted 10 months ago #
Hey Olederer, have you tried clicking into the text box in the widget? The WYSIWYG editor then opens up for you, and you save that HTML back into the widget.
If nothing happens when you click in the text box on the widget, see if you can disable other plugins and see which one might be conflicting.
Posted 10 months ago #
Hi Olederer, hmmm..
Which browser are you using? You have to click the textarea for the TinyMCE overlay to show up.. (Probably a stupid note, but worth a try.) If you could provide me with some more details about your WP installation it's easier for me to try to replicate the problem. (think: browser, other plugins, etc.. )
Posted 10 months ago #
@Japh, yes of course strange is that it works on a second blog very well.
Posted 10 months ago #
My problem is solved!
Don't disable the visual editor for the user in question ;)
Great Plugin Danny!
Posted 10 months ago #
Yup - works fine now. Good work, Danny - thanks for the quick response.
Andy
Posted 10 months ago #
i have the same problem after upgrading to 3.2,
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'wp_tiny_mce_preload_dialogs' was given in blog/wp-includes/plugin.php on line 405
I think the problem is that I have installed a plugin with an editor Enrichment has a line of code that says:
function show_tinyMCE() {
add_action('admin_print_footer_scripts', 'wp_tiny_mce_preload_dialogs', 30 );
I tried changing that line of code as it says "Japh" but follows the same mistake
Can you help me?
Posted 10 months ago #
Lamenteinc, contact the plugin author or wait for WordPress 3.2.1 since it will (most likely) be fixed there.
Posted 10 months ago #
@lamenteinc: Have you tried updating to the latest version of the plugin? The author has implemented a fix in this version that has sorted the issue for me. Hopefully it works for you too :)
You must log in to post.
