Skip to:
Content
Pages
Categories
Search
Top
Bottom

PHP Errors


  • Sophos Creative
    Participant

    @keiser-media

    11 years, 1 month ago

    I am getting these errors on a clean install of BuddyPress:

    Strict Standards: Only variables should be assigned by reference in /Applications/MAMP/htdocs/oswnetwork/wp-content/plugins/buddypress/bp-loader.php on line 602

Strict Standards: Non-static method BP_XProfile_ProfileData::get_value_byid() should not be called statically in /Applications/MAMP/htdocs/oswnetwork/wp-content/plugins/buddypress/bp-xprofile/bp-xprofile-functions.php on line 175

Strict Standards: Non-static method BP_Core_User::get_core_userdata() should not be called statically in /Applications/MAMP/htdocs/oswnetwork/wp-content/plugins/buddypress/bp-members/bp-members-functions.php on line 161

Strict Standards: Non-static method BP_Core_Notification::get_all_for_user() should not be called statically in /Applications/MAMP/htdocs/oswnetwork/wp-content/plugins/buddypress/bp-members/bp-members-notifications.php on line 86

    I am using WP version 3.6.1 with the default theme “Twenty Thirteen” and this is the only active plugin.

Viewing 5 replies - 1 through 5 (of 5 total)

  • celticdancer
    Participant

    @celticdancer

    11 years, 1 month ago

    I have the exact same error. Did a clean install three times. No change 🙁


    danbp
    Participant

    @danbp

    11 years, 1 month ago

    Hi @keiser-media @celticdancer,

    The usual answer in this case is: these notice are only notice. A kind of weather report: all hear and read about, but who cares ?

    If you see the notice on a production site, deactiveate the debug define in wp-config.

    Don’t be afraid by “strict standards” messages. It’s probably because you use PHP 5.4.x or higher. These versions are a little bugy actually. And most shared server are yet under 5.3.x

    More here

    PS: i encounter the same problem (php 5.4.12) 😀


    Sophos Creative
    Participant

    @keiser-media

    11 years, 1 month ago

    These notices aren’t “only notices.” They mean that something isn’t coded properly. So obviously I care as it is preventing me from doing my job. I am not afraid of strict standards messages as I have fixed any that exist within my own projects. Dismissal of an issue does not fix it.

    Here is a better solution: https://buddypress.trac.wordpress.org/ticket/5108


    shanebp
    Moderator

    @shanebp

    11 years, 1 month ago

    @keiser-media
    Please add ‘your’ notices to that ticket, if you haven’t already done so.


    Hugo Ashmore
    Participant

    @hnla

    11 years, 1 month ago

    @keiser-media As mentioned above please update the ticket then. The forum isn’t the place for this kind of thing, it won’t necessarily come to the attention of the core devs whereas tickets will do, also anyone is welcome to provide patches to help the project along.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘PHP Errors’ is closed to new replies.

Topic Info

Skip to toolbar