The admin area of WordPress 7.2 loads scripts and stylesheets individually instead of bundling them into large packages. The two files load-scripts.php and load-styles.php, which previously handled the bundling, are deprecated according to the WordPress Developer Blog of November 13, 2026. The release is planned for December 8, 2026.
The change affects the admin area, not the site your visitors see. You will notice it with custom plugins, firewall rules, or a Content Security Policy, because references to the old files may be found there.
What is changing in the admin area?
Until now, WordPress delivered a bundled package for each admin page. Dr. Web classifies this as a legacy of the HTTP/1.1 era: the package was difficult to reuse in the browser cache. Under HTTP/2, individual files load in parallel, and all admin pages access the same cached files.
The WordPress Developer Blog names three consequences:
- WordPress loads the files individually and prefetches what the next screen will probably need.
- load-scripts.php and load-styles.php are deprecated.
- Some scripts appear in the footer instead of the head.
Dr. Web goes further in its article on Beta 1: since Beta 1, both files respond with status code 410 (Gone) without starting WordPress. The background is the security vulnerability CVE-2018-6389, through which a server could be overloaded with requests to load-scripts.php. WordPress no longer reads the constant CONCATENATE_SCRIPTS.
How much time is left for testing?
Beta 5 is available. According to the Developer Blog, Release Candidate 1 follows on November 17, 2026, and the final version is due on December 8. Dr. Web additionally names Release Candidates 2 and 3 on November 24 and December 1.
WordPress 7.2 until the release
Planned dates for testing your site
- November 17, 2026Release Candidate 1
- November 24, 2026Release Candidate 2
- December 1, 2026Release Candidate 3
- December 8, 2026Final version
Dates may change; they are planned values.
Sources: WordPress Developer Blog, Dr. Web
What could break on your site?
Dr. Web recommends checking these points on a staging copy:
- Firewall rules, CDN settings, and security plugins with entries for load-scripts.php
- the constant CONCATENATE_SCRIPTS in wp-config.php
- Plugins that call deprecated functions such as script_concat_settings(); the debug log shows them
- a Content Security Policy: worker-src needs the entry blob:, otherwise the media library's image processing runs via the server again
- Image plugins that hook into wp_image_editors or image_make_intermediate_size, because both hooks do not take effect during processing in the browser
The last two points belong to a second new feature: According to the WordPress announcement for Beta 1, the media library resizes, compresses, and converts images directly in the browser before they are uploaded.
Our assessment: The benefit depends on HTTP/2. Whether your hosting supports it is shown in the network view of your browser's developer tools in the Protocol column, where it says h2. If it says http/1.1, check on the staging copy whether the admin area loads noticeably slower.
What this means for you
It's best to first create a staging copy and install Beta 5 there, for example with the WordPress Beta Tester plugin or the command wp core update --version=7.2-beta5, both of which the Developer Blog mentions. Ideally, keep the debug log running, click through the post list, media library, and plugin settings, and note every message about deprecated functions.
Afterwards, search your files for load-scripts.php, for example with the command grep -rn load-scripts.php in the wp-content folder, and feel free to remove CONCATENATE_SCRIPTS from wp-config.php. You can see firewall and CDN rules in the respective dashboard. Before the actual update, create a backup, as Dr. Web also advises.
The WordPress Developer Blog published the overview on November 13, 2026.
Sources
