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

WordPress Trac noreply at wordpress.org
Sun Feb 9 17:35:43 UTC 2014


#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:
-----------------------------------------------+---------------------------

Comment (by wonderboymusic):

 After thinking about it, I don't think `delete/add` is an upgrade from
 `set`. I can see the benefit of `add` when your goal is "I want something
 in the cache, no matter what, so as long as its there, we're good" but
 `set` is more appropriate for "the value needs to be overwritten, no
 matter what."

 Also, for cleanliness' sake, I can see the reason to use the `terms`
 bucket, so I will probably make that change, but WP doesn't give you any
 way to invalidate by group, so the change is really arbitrary.

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


More information about the wp-trac mailing list