stripslashes in update_usermeta messes up meta_values for arrays/objects

[stm]

the change made in rev [4382] caused a problem when trying to set a non-string as a meta_value.
There should be a check made to see if the object is a string before doing a stripslashes.

ie.

if ( !is_array($meta_value) && !is_object($meta_value) )
    $meta_value = stripslashes($meta_value);

I found this because it was making the Administrator capabilites be 'Array' in the db instead of the serialized array of capabilities it was supposed to be set to.

[stm]

sorry, forgot to mention the file it's in:

source:trunk/wp-includes/user.php@4383#L118​

[markjaquith]

Eek, good catch. I think there's one other place this has to be fixed. I'll get that taken care of later tonight.

[markjaquith]

(In [4395]) Only run stripslashes() on strings in update_usermeta(). Props stm. fixes #3240

[markjaquith]

(In [4396]) Only run stripslashes() on strings in update_usermeta(). Props stm. fixes #3240