I had the same problem with block inline css not loading on my server after deploying files and database from a local development environment.
@mevanloon put me on the right track and I confirm that deleting the transient wp_core_block_css_files from the database on the server fixed the issue. The transient caches the full path of all the css files in wp-includes/blocks/. After a migration/deployment the paths don’t work but the transient needs to be deleted before being automatically re-generated with the new correct paths.
Deleting the transient after every deployment felt a bit cumbersome so I kept digging and came across this article that mentions the constant WP_DEVELOPMENT_MODE introduced with WordPress 6.3. Adding define( ‘WP_DEVELOPMENT_MODE’, ‘all’ );? in my wp-config.php in dev and leaving it empty (or not defining it) in production solves the issue because it prevent exactly that type of caching and transient issues.
-
This reply was modified 1 year, 6 months ago by sylverbear.
