Take the 2-minute tour ×
WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. It's 100% free, no registration required.

On a freshly built site running version 3.1.3 with the twentyten theme active and no plugins, when I click on "Media" to go the media manager, I'm getting this error:

Warning: explode() expects parameter 2 to be string, array given in C:\xampplite\htdocs\testsite\wp-includes\query.php on line 2390

Warning: in_array() expects parameter 2 to be array, null given in C:\xampplite\htdocs\testsite\wp-includes\query.php on line 2399

Warning: in_array() expects parameter 2 to be array, null given in C:\xampplite\htdocs\testsite\wp-includes\query.php on line 2399

Warning: in_array() expects parameter 2 to be array, null given in C:\xampplite\htdocs\testsite\wp-includes\query.php on line 2399

Warning: in_array() expects parameter 2 to be array, null given in C:\xampplite\htdocs\testsite\wp-includes\query.php on line 2399

Warning: in_array() expects parameter 2 to be array, null given in C:\xampplite\htdocs\testsite\wp-includes\query.php on line 2399

Warning: in_array() expects parameter 2 to be array, null given in C:\xampplite\htdocs\testsite\wp-includes\query.php on line 2399

Warning: in_array() expects parameter 2 to be array, null given in C:\xampplite\htdocs\testsite\wp-includes\query.php on line 2399

Warning: in_array() expects parameter 2 to be array, null given in C:\xampplite\htdocs\testsite\wp-includes\query.php on line 2399

Warning: Cannot modify header information - headers already sent by (output started at C:\xampplite\htdocs\testsite\wp-includes\query.php:2390) in C:\xampplite\htdocs\testsite\wp-includes\functions.php on line 851

Warning: Cannot modify header information - headers already sent by (output started at C:\xampplite\htdocs\testsite\wp-includes\query.php:2390) in C:\xampplite\htdocs\testsite\wp-includes\functions.php on line 852

share|improve this question

1 Answer 1

up vote 3 down vote accepted

Quick look at source for that version shows parsing post_status argument. It's probably this bug that got fixed in 3.2.

Upgrade. :)

share|improve this answer
    
Thanks. That was it. –  N2Mystic Jul 15 '11 at 23:27

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.