[wp-trac] [WordPress Trac] #23330: Allow autoloading all options, not just autoload = yes options
WordPress Trac
noreply at wordpress.org
Thu Jan 31 13:52:57 UTC 2013
#23330: Allow autoloading all options, not just autoload = yes options
--------------------------+-----------------------------
Reporter: ryan | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Future Release
Component: Cache | Version: 3.5.1
Severity: normal | Resolution:
Keywords: |
--------------------------+-----------------------------
Comment (by ryan):
Replying to [comment:3 rmccue]:
> -1. I'm going to have to disagree with this. If you store custom objects
in the database, those fail to load thanks to `unserialize` being run
before your classes get redefined. There's no way to force these to be
reloaded from the database once they are loaded into the object cache, so
you're stuck.
>
> (I experienced this problem yesterday and it was incredibly annoying.)
That's a good reason for not ignoring autoload by default.
Since this can happen to autoload = yes options too, perhaps we can
finagle a method for postponing unserialize for custom objects.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/23330#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list