[2.0.12] cache not work?

[inter]

Yesterday I updated the forum and I now have all the cache does not work. My cache system is file storage.

Code Select Expand

cache_get_data('modSettings')

return false

[inter]

PHP Version: 5.6

[aegersz]

I think this is related to the Upgrade's serialization related change and there is already at least one Topic that reports multiple issues when caching is set on.

[vbgamer45]

it's probably most like do to this

Code Select Expand


function _safe_unserialize($str)
{
// Input exceeds 4096.
if(strlen($str) > 4096)
return false;


If you take out that if statement it probably will work

[inter]

imho. Before the function "cache_get_data" returns "null" type is now a new type "false" and now the old code may break.

[aegersz]

it's probably most like do to this

Code Select Expand


function _safe_unserialize($str)
{
// Input exceeds 4096.
if(strlen($str) > 4096)
return false;


If you take out that if statement it probably will work

i tried that on my SimplePortal Shoutbox cache issue (Subs.php) and it doesn't stop the cache from being processed correctly upon page reload. any idea why this would be ?

[inter]

I am not right, earlier the "false" boolean type could return too. But earlier at me he never came back.

[asmith]

I revert my 2.0.12 update because of the same cache problem.

it's probably most like do to this

Code Select Expand


function _safe_unserialize($str)
{
// Input exceeds 4096.
if(strlen($str) > 4096)
return false;


If you take out that if statement it probably will work

That fixes the problem, but I'm not sure that's the proper way.

There's cache_put_data() function which is still using serialize(), shouldn't it change to start using safe_serialize()?

[nend]

@asmith
safe_serialize isn't used AFAIK.

As far as the issue, there was a problem with the release and an older revision got released instead of the actual 2.0.12 we had planned. Rest assure we are working on getting the correct revision out soon.

[feline]

Remove the part:

Code Select Expand


// Input exceeds 4096.
if(strlen($str) > 4096)
return false;

the php unserialize don't have any limits ...

[asmith]

@feline,

should I do it manually or the update is fixed now?

[vbgamer45]

Not fixed yet waiting on a patch release.

[Adrek]

@asmith
safe_serialize isn't used AFAIK.

As far as the issue, there was a problem with the release and an older revision got released instead of the actual 2.0.12 we had planned. Rest assure we are working on getting the correct revision out soon.

any news about new patch?

[Kindred]

as noted, it is being worked on

[Antes]

Please test the issue again in SMF 2.0.13 if you are having issue open a new topic with [SMF 2.0.13] tag on topic.

Thank you.