3.0/caching issues

[Sesquipedalian]

Fixes some issues with caching.

First, there were some problems with the Sqlite cache API that have been fixed in 17f9186.

Second, and more importantly, 17fdb6e changes how we convert cached data to strings. Instead of using json_encode() and json_decode(), we are now using serialize() and unserialize(). This is necessary because in SMF 3.0 we need to cache objects. For example, when caching recent events, we pass a collection of SMF\Calendar\EventOccurrence objects to be cached. Encoding that to JSON loses data and the objects cannot be reconstructed when retrieved, resulting in nasty errors.

[tyrsson]

Fixes some issues with caching.

First, there were some problems with the Sqlite cache API that have been fixed in 17f9186.

Second, and more importantly, 17fdb6e changes how we convert cached data to strings. Instead of using json_encode() and json_decode(), we are now using serialize() and unserialize(). This is necessary because in SMF 3.0 we need to cache objects. For example, when caching recent events, we pass a collection of SMF\Calendar\EventOccurrence objects to be cached. Encoding that to JSON loses data and the objects cannot be reconstructed when retrieved, resulting in nasty errors.

Sounds familiar.... Sorry, I have not been able to finish the psr compliance work :)

I would follow the usage here:
https://wiki.php.net/rfc/custom_object_serialization#:~:text=The%20__serialize()%20and,if%20it%20represented%20object%20properties.

[Sesquipedalian]

Sounds familiar....

Yup