[wp-trac] [WordPress Trac] #22223: Potential for post cache corruption since r21735

WordPress Trac noreply at wordpress.org
Fri Oct 19 02:03:34 UTC 2012


#22223: Potential for post cache corruption since r21735
--------------------------+------------------
 Reporter:  ryan          |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  3.5
Component:  Cache         |     Version:
 Severity:  normal        |  Resolution:
 Keywords:                |
--------------------------+------------------

Comment (by nacin):

 Replying to [comment:14 ryan]:
 > We might still want to use proper properties with defaults. We're seeing
 some homebrew objects that don't even have post_type set, resulting in
 warnings down the line and extra queries because the new magic get tries
 to fetch post_type from meta.

 Would `__get()` fire in that case? The property is declared, so `__get()`
 would only get hit if someone takes a WP_Post object and then unsets a
 property.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/22223#comment:15>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list