Missing wp-includes/css/classic-themes.min.css stylesheet

[bilalmughl]

Bug Report

Description

A warning is being displayed when adding new pattren using Hello Elementor 3.0.1 Theme.
Warning: file_get_contents(/wordpress/wp-includes/css/classic-themes.min.css): Failed to open stream: The specified file or directory does not exist in /wordpress/wp-includes/script-loader.php on line 14
Warning: Cannot modify header information - headers already sent by (output started at /wordpress/wp-includes/script-loader.php:14)

Environment

• WordPress: 6.5-beta1
• PHP: 8.0.30-dev
• Server: PHP.wasm
• Database: WP_SQLite_Translator (Server: 5.5 / Client: 3.40.1)
• Browser: Chrome 121.0.0.0
• OS: Windows 10/11
• Theme: Hello Elementor 3.0.1
• MU Plugins:
  • 0-playground.php
  • 0-sqlite.php
  • WordPress WXZ Exporter 0.1
• Plugins:
  • Create Block Theme 1.13.8
  • Debug Bar 1.1.4
  • Health Check & Troubleshooting 1.7.0
  • Test Reports 1.1.0
  • User Switching 1.7.2
  • WordPress Importer Git loader 0.8.2

Steps to Reproduce

2. 🐞 Bug occurs.

Expected Results

1. ✅ The new pattern should be added without any warnings.

Actual Results

1. ❌ Warnings are displayed:

Warning: file_get_contents(/wordpress/wp-includes/css/classic-themes.min.css): Failed to open stream: The specified file or directory does not exist in /wordpress/wp-includes/script-loader.php on line 14
Warning: Cannot modify header information - headers already sent by (output started at /wordpress/wp-includes/script-loader.php:14)

Additional Notes

• This issue occurs when using Hello Elementor 3.0.1 Theme while attempting to add a new pattern.

Supplemental Artifacts

Screenshot:
​https://take.ms/Ca9Rv
Video:
​https://take.ms/QP6Yd

[swissspidy]

I just downloaded WordPress 6.5 Beta 1 from ​https://wordpress.org/news/2024/02/wordpress-6-5-beta-1/ and the wp-includes/css/classic-themes.min.css file definitely does exist. So this seems like an issue with Playground.

[bilalmughl]

The problem occurred during testing on Playground.

[karmatosed]

Thank you for reporting this @bilalmughl. I am actually unable to replicate this today on Playground using the latest. However, that doesn't mean this issue doesn't still exist for you. If that is the case, though, this would be something to get resolved through bug reporting here: ​https://github.com/WordPress/wordpress-playground/issues/new.

As I cannot replicate today, I will close with 'works for me,' but that doesn't mean that you might not need to explore this issue further through Playground. Thank you, everyone, for collaborating on this.