Error Messages since upgrading to WordPress 3.6

Home Forums WPAlchemy Error Messages since upgrading to WordPress 3.6

Tagged: 

This topic contains 5 replies, has 6 voices, and was last updated by  bepcongnghiep 6 months, 3 weeks ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #2601

    Patrick Samphire
    Participant

    I’ve been getting the following error messages since upgrading to WordPress 3.6:

    Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method WPAlchemy_MetaBox::_global_head() should not be called statically in /wp-includes/plugin.php on line 406

    Strict Standards: Non-static method WPAlchemy_MetaBox::_is_post() should not be called statically in /wp-content/wpalchemy/MetaBox.php on line 1352

    Strict Standards: Non-static method WPAlchemy_MetaBox::_is_post_or_page() should not be called statically in /wp-content/wpalchemy/MetaBox.php on line 986

    Strict Standards: Non-static method WPAlchemy_MetaBox::_get_current_post_type() should not be called statically in /wp-content/wpalchemy/MetaBox.php on line 1024

    Strict Standards: Non-static method WPAlchemy_MetaBox::_is_page() should not be called statically in /wp-content/wpalchemy/MetaBox.php on line 1352

    Strict Standards: Non-static method WPAlchemy_MetaBox::_is_post_or_page() should not be called statically in /wp-content/wpalchemy/MetaBox.php on line 1005

    Strict Standards: Non-static method WPAlchemy_MetaBox::_get_current_post_type() should not be called statically in /wp-content/wpalchemy/MetaBox.php on line 1024

    Am I doing something wrong, or is this something that WordPress has changed? I didn’t get these messages with 3.5.

    Thanks!

    #2603

    blacksrv
    Participant

    I’m having the same problem.

    #2604

    Phyteau
    Participant

    I am also having the very same problem…

    #2637

    cibulka
    Participant

    Same problem here. Any news?

    #2667

    Pirenko
    Participant

    It seems that I have created a workaround on this.
    Here’s some help: http://www.pirenko.com/blog/2013/10/17/wpalchemy-warnings-fix/

    #2745

    bepcongnghiep
    Participant
Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.