Edit report at https://bugs.php.net/bug.php?id=61042&edit=1
ID: 61042
Comment by: spamfry at gmail dot com
Reported by: vigano dot n at clxeurope dot com
Summary: unserialize issue
Status: Duplicate
Type: Bug
Package: Arrays related
Operating System: Linux Centos
PHP Version: 5.3.10
Block user comment: N
Private report: N
New Comment:
This seems to be related, even though I'm in PHP 5.3.8, and I'm not using
unserialize() at all:
$obj = new stdClass;
$obj->{0} = 'foo';
var_dump(isset($obj->{0}));
$arr = (array)$obj;
var_dump($arr);
var_dump(isset($arr[0]));
Output:
bool(true)
array(1) {
["0"]=>
string(3) "foo"
}
bool(false)
So apparently you can't access numeric properties after casting an object to an
array.
Previous Comments:
------------------------------------------------------------------------
[2012-04-09 18:32:03] spamfry at gmail dot com
I am experiencing this bug in PHP 5.3.10. As previously mentioned, both
isset($uns[0]) and isset($uns["0"]) return false, so this is not merely a
matter
of the data type of the array key, so it appears to be different from what is
described in #55798. Was the issue resolved when #55798 was resolved?
------------------------------------------------------------------------
[2012-02-13 11:20:39] cataphr...@php.net
Again:
The reason why
$arr = (object)array("value");
$uns = (array)unserialize(serialize($arr));
var_dump($uns);
var_dump(isset($uns["0"]));
does not work, but this does
$arr = (object)array("value");
$uns = (array)$arr;
var_dump($uns);
var_dump(isset($uns["0"]));
is actually because the object $arr is broken (has a numeric property), while
this is fixed by the composition of serialize/unserialize (since 5.3.9).
The bug you're experiencing is unrelated to unserialize, it's just that there
used to be a bug in unserialize that would cancel out another bug that still
exists, and that you can reproduce with:
//$arr = (object)array("value");
$arr = new stdClass;
$arr->{'0'} = "value";
//$uns = (array)unserialize(serialize($arr));
$uns = (array)$arr;
var_dump($uns);
var_dump(isset($uns["0"]));
------------------------------------------------------------------------
[2012-02-10 13:07:07] vigano dot n at clxeurope dot com
A possible workaround is serializing and unserializing again. Look at this
piece of code:
$arr = (object)array("value0", "value1");
$uns = unserialize(serialize((array)unserialize(serialize($arr))));
var_dump($uns);
var_dump(isset($uns["0"]));
var_dump(isset($uns[0]));
var_dump(isset($uns["1"]));
var_dump(isset($uns[1]));
The result is:
array(2) { [0]=> string(6) "value0" [1]=> string(6) "value1" } bool(true)
bool(true) bool(true) bool(true)
This definitively confirm my idea that bug #55798 has nothing to do with this
issue.
------------------------------------------------------------------------
[2012-02-10 12:22:19] vigano dot n at clxeurope dot com
In addition, to be honest I don't believe hat this problem "is that these
strings are not converted to numbers when casting to an array".
The following code, where conversion is not required, doesn't work as well:
$arr = (object)array("value");
$uns = (array)unserialize(serialize($arr));
var_dump($uns);
var_dump(isset($uns["0"]));
result:
array(1) { ["0"]=> string(5) "value" } bool(false)
------------------------------------------------------------------------
[2012-02-10 12:14:09] vigano dot n at clxeurope dot com
Anyway the problem affects only unserialized and cast objects.
The following code works properly also with PHP 5.3.9/10:
$arr1 = array("0" => "string");
var_dump(isset($arr1["0"]));
var_dump(isset($arr1[0]));
returning:
bool(true) bool(true)
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=61042
--
Edit this bug report at https://bugs.php.net/bug.php?id=61042&edit=1
