|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #77872 private/protected __serialize/__unserialize triggers a warning
Submitted: 2019-04-09 13:51 UTC Modified: 2019-04-09 15:39 UTC
From: nicolas dot grekas+php at gmail dot com Assigned:
Status: Open Package: *General Issues
PHP Version: Next Minor Version OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
21 + 15 = ?
Subscribe to this entry?

 [2019-04-09 13:51 UTC] nicolas dot grekas+php at gmail dot com
When the new __serialize/__unserialize method are made protected or private, a warning is thrown.
Throwing an Error might be better.

Test script:
class foo
    private function __serialize()
        return [123];

    public function __unserialize($a)

$f = new foo();

$s = serialize($f);

Expected result:
"Fatal error: Uncaught Error: Call to private method foo::__serialize()" or similar

Actual result:
Warning: Invalid callback foo::__serialize, cannot access private method foo::__serialize() in /var/www/html/test.php on line 22


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2019-04-09 15:31 UTC]
This is a standard warning generated by the internal call mechanism, not by the serialization handling. If we change something here it should probably only be in PHP 8 and for all users of the mechanism.
 [2019-04-09 15:39 UTC] nicolas dot grekas+php at gmail dot com
Changing that for PHP8 would be great then, yes!
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Sat May 08 07:01:23 2021 UTC