This has been resolved with v3.0.2. My apologies for anything that broke.
Version 3.0 was not intended to be backwards compatible and shifted to using <i>native</i> session functionality within PHP rather than a custom (admittedly buggy) object implementation. Some helpful devs in the community have contributed a backwards-compatibility patch, however, that restores functionality if you’re still using the WP_Session
object.
Updating to v3.0.2 should now be possible without losing track of your sessions – though any sessions active before the update will be reset as the new version uses a different storage mechanism.
Moving forward, I’d encourage you to upgrade your usage of the WP_Session
object to using native $_SESSION
references as the former is deprecated and will eventually be removed.