update_site_option can't handle saving objects

[griffinjt]

When using the update_option function, if an object is passed as the value, the function automatically clones and serializes (if necessary) the value before saving, and then get_option unserializes (if necessary) when retrieving the data.

update_site_option does not do this, so it cannot handle saving objects unless you add a workaround using the pre_update_site_option_* filter or just check for serializing when saving and retrieving the data. One would expect for update_site_option to be able to handle objects, too.

Wow, I am blind. I see the maybe_serialize now in update_site_option. Closing due to Monday morning madness.