Actions
Bug #79168
closedCache: Throw exception if unserialize in VariableFrontend->get() returns false
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-01-05
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
In the VariableFrontend, values are serialized() in set(). Thus, it should NOT happen that unserialize() fails in get(). This only happens if the backend implementation or DB is broken.
Currently, this issue is not turned into an exception.
However, this is hard to fix if the value "boolean false" is serialized. This then can not be distinguished from the "unserialize was unsuccessful" case.
The only difference is that unserialize throws a notice in those cases - which are suppressed in the core ...
I guess this can not be solved easily for now (and fiddling with the error reporting for each cache call isn't nice), but wanted to have that behavior documented.
Actions