• Resolved woom

    (@woom)


    Get this Warning when in products of WooCommerce 2.3.8

    Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, ‘disable_emojis_tinymce’ was given in ../../wp-includes/plugin.php on line 213

    /* ---------------------------------------------------------------------------
     * Disable the emoji's
     * --------------------------------------------------------------------------- */
     function disable_emojis() {
    	remove_action( 'wp_head', 'print_emoji_detection_script', 7 );
    	remove_action( 'admin_print_scripts', 'print_emoji_detection_script' );
    	remove_action( 'wp_print_styles', 'print_emoji_styles' );
    	remove_action( 'admin_print_styles', 'print_emoji_styles' );
    	remove_filter( 'the_content_feed', 'wp_staticize_emoji' );
    	remove_filter( 'comment_text_rss', 'wp_staticize_emoji' );
    	remove_filter( 'wp_mail', 'wp_staticize_emoji_for_email' );
    	add_filter( 'tiny_mce_plugins', 'disable_emojis_tinymce' );
    }
    add_action( 'init', 'disable_emojis' );

    https://wordpress.org/plugins/disable-emojis/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Ryan Hellyer

    (@ryanhellyer)

    That makes no sense to me at all right now, but I’ll look into it and try to work out a solution for you.

    Plugin Author Ryan Hellyer

    (@ryanhellyer)

    I suspect this is caused by WooCommerce doign something weird with the tiny_mce_plugins filters. To work around this, I’ve set the filter to output an empty array when the $plugins variable is not an array (probably when it’s just empty/null).

    Hopefully that will fix this issue. If not, please let me know 🙂

    Plugin Author Ryan Hellyer

    (@ryanhellyer)

    Version 1.5 is the release I just created which has this new feature ^

    Thread Starter woom

    (@woom)

    Works fine, thank you!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Warning: call_user_func_array()’ is closed to new replies.