[wp-trac] [WordPress Trac] #59111: A stale register_core_block_style_handles cache can cause styles not to load

[WordPress Trac]

#59111: A stale register_core_block_style_handles cache can cause styles not to
load
--------------------------+--------------------------
 Reporter:  joemcgill     |       Owner:  joemcgill
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  6.3.2
Component:  Themes        |     Version:  6.3
 Severity:  major         |  Resolution:
 Keywords:  has-patch     |     Focuses:  performance
--------------------------+--------------------------

Comment (by joemcgill):

 Replying to [comment:35 kimannwall]:
 > Facing a similar issue here, not related to staging and dev, but rather
 a production environment hosted by Pagely.
 >
 > The transient has been deleted via CLI and continues to rebuild with
 paths to CSS files like:
 >
 > {{{
 > /wordpress-versions/6.3.1/wp-includes/blocks/archives/editor.css
 > }}}
 >
 > Which doesn't exist within the context of the site and cannot be used to
 build the final inline CSS needed.

 Thanks for the context, @kimannwall. I'm not sure how the `wp-includes`
 location is being manipulated on your hosting platform, but the additional
 use case is helpful in terms of things to test against. I think the
 approach being worked on in [https://github.com/WordPress/wordpress-
 develop/pull/5052 PR5052] should fix this.

 Since you're unable to set a development mode as a workaround, perhaps
 adding something like this filter as a plugin or your theme's
 `functions.php` file might work until a minor release is released with
 this fix:


 {{{#!php
 <?php
 add_filter( 'pre_transient_wp_core_block_css_files',
 '__return_empty_array' );
 }}}

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