[wp-trac] [WordPress Trac] #59719: Revise caching approach for theme files

[WordPress Trac]

#59719: Revise caching approach for theme files
-----------------------------------+--------------------------
 Reporter:  flixos90               |       Owner:  joemcgill
     Type:  task (blessed)         |      Status:  closed
 Priority:  high                   |   Milestone:  6.5
Component:  Themes                 |     Version:
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  2nd-opinion has-patch  |     Focuses:  performance
-----------------------------------+--------------------------
Changes (by joemcgill):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 The original purpose of this issue, which was to consolidate conversation
 about the caching strategy for block theme files that was happening across
 various issues like #59600, #59633, and #60120 has been fulfilled by
 [comment:13 the discussion summarized by this comment]. For that reason,
 I'm closing this as fixed and we can continue any implementation detail
 discussion on #59600, which I've modified to include block patterns in
 addition to the template files. I've also update the PR description of
 [https://github.com/WordPress/wordpress-develop/pull/6137 this PR] to
 point to #59600.

 To summarize the main results of this issue:

 * Block theme template related files will now be cached in a new
 `theme_files` cache group.
 * We will explore the use of persistent caching for this group in #59600.
 * All caches in this group should respect `WP_DEVELOPMENT_MODE`.
 * Persistent caching strategies should be resilient to files being
 directly modified on production servers (e.g., transients must use
 expiration times).

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