[wp-trac] [WordPress Trac] #22526: Changing category doesn't invalidate cache

[WordPress Trac]

#22526: Changing category doesn't invalidate cache
-----------------------------------------------+---------------------------
 Reporter:  Whissi                             |       Owner:
     Type:  defect (bug)                       |  wonderboymusic
 Priority:  normal                             |      Status:  reopened
Component:  Cache API                          |   Milestone:  3.9
 Severity:  normal                             |     Version:  3.4.2
 Keywords:  has-patch needs-docs dev-feedback  |  Resolution:
                                               |     Focuses:
-----------------------------------------------+---------------------------
Changes (by kovshenin):

 * keywords:  has-patch needs-docs => has-patch needs-docs dev-feedback
 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 r27101 introduces a bunch of new tax_last_changed cache groups, and each
 one will most likely have a single key. Perhaps we can use the existing
 `terms` group to hold that? In `get_taxonomy_last_changed` you can use
 `wp_cache_add()` instead of `_set()` which I believe can be faster on some
 cache backends.

 Also, this seems to introduce quite a lot of new stuff, all of it for the
 little bug we're trying to fix. Why can't we just use
 `clean_object_term_cache` like we do in `wp_delete_term`? See
 [attachment:22526.2.diff], it passes the unit test added in r27099.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/22526#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform