[wp-trac] [WordPress Trac] #60120: Add cache group to block pattern cache

[WordPress Trac]

#60120: Add cache group to block pattern cache
--------------------------+--------------------------
 Reporter:  spacedmonkey  |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.5
Component:  Themes        |     Version:  6.4
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:  performance
--------------------------+--------------------------
Changes (by joemcgill):

 * keywords:   => needs-patch
 * type:  enhancement => defect (bug)
 * milestone:  Future Release => 6.5


Comment:

 I agree that we should address this. Originally, block patterns were going
 to be cached to a transient, but no expiration strategy was set, nor are
 transients easily clearable. This concern was raised in #59633.

 As a compromise, this was moved to the global cache group so that sites
 with an object cache would still get the benefits of persistent caching,
 while we considered a better wholistic caching strategy for expensive
 operations related to getting and parsing data from theme files in block
 themes (see: #59719).

 Generally, it would make sense to cache all of these files to the `themes`
 cache group, but that group is non-persistent by default, unless someone
 has opted in to group being persistent by filtering the
 `wp_cache_themes_persistently` value.

 Once a wholistic strategy is determined in #59719, we can apply that
 strategy to the pattern cache methods in `WP_Theme`.

 Moving this to the 6.5 milestone.

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