Skip to:
Content
Pages
Categories
Search
Top
Bottom

wrond datatype for second argument – headers already sent


  • zanzoon
    Participant

    @zanzoon

    15 years, 11 months ago

    I get the following error when I click setting in the backend then save changes:

    Warning: array_search() [function.array-search]: Wrong datatype for second argument in /wp-admin/includes/plugin.php on line 1044

    Warning: array_search() [function.array-search]: Wrong datatype for second argument in wp-admin/includes/plugin.php on line 1044

    Warning: array_search() [function.array-search]: Wrong datatype for second argument in wp-admin/includes/plugin.php on line 1044

    Warning: array_search() [function.array-search]: Wrong datatype for second argument in /wp-admin/includes/plugin.php on line 1044

    Warning: Cannot modify header information – headers already sent by (output started at //wp-admin/includes/plugin.php:1044) in /wp-includes/pluggable.php on line 856

    btw, the page in the browser is: http://zanzoon.com/wp-admin/options.php

    thanks a lot :D

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

  • Burt Adsit
    Participant

    @burtadsit

    15 years, 11 months ago

    This sounds like an mu problem zanzoon. bp doesn’t have much to do with the backend of mu. Have you searched the mu forums? https://mu.wordpress.org/forums/

    Have you googled for that error msg with ‘wordpress’ as one of the keys?

    Looks like you are trying to modify a setting in the options page of mu and it doesn’t like what you are doing. I can’t tell you why from the info you’ve given.


    zenseeker
    Participant

    @zenseeker

    15 years, 11 months ago

    I started getting these when I installed the latest trunk of MU. I ratcheted back to wpmu trunk r1574 and they went away. Hope that helps a little.


    Burt Adsit
    Participant

    @burtadsit

    15 years, 11 months ago

    It’s a bug in the latest mu r1589. The function remove_option_whitelist() in plugin.php is not checking to see if it’s going to reference a var that has been unset(). It is called by mu_options() in mu.php and in there it unsets() an element in the $options array.

    Why? I dunno but it does. Then it asks remove_option_whitelist() to get rid of something that doesn’t exist anymore. It should check for isset(), is_array() but it’s not.

    I posted it in the mu trac. Gotta wait til the fix floats thru svn.

    “You aren’t doing anything wrong. Stop trying to do it right.”

    (that was for trent)

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘wrond datatype for second argument – headers already sent’ is closed to new replies.

Topic Info

Topic Tags

Skip to toolbar