Changes between Version 1 and Version 2 of Ticket #30779, comment 1
- Timestamp:
- 12/20/2014 01:40:35 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #30779, comment 1
v1 v2 1 This may happen because `class.wp-scripts.php` is included from `script-loader.php` which is included from `wp-admin/load-scripts.php` and `wp-admin/load-styles.php`. Both of these run "outside" of WordPress and don't load functions.php. If that happensa workaround would be to add `define('CONCATENATE_SCRIPTS', false);` or `define('SCRIPT_DEBUG', true);` to wp-config.php.1 In theory this is possible to happen because `class.wp-scripts.php` is included from `script-loader.php` which is included from `wp-admin/load-scripts.php` and `wp-admin/load-styles.php`. Both of these run "outside" of WordPress and don't load functions.php. If that is ever triggered a workaround would be to add `define('CONCATENATE_SCRIPTS', false);` or `define('SCRIPT_DEBUG', true);` to wp-config.php. 2 2 3 However this won't bring the site down. It will fail to output concatenated scripts or styles in the admin. Looking at the (only?) report in the forum, this sounds more like a failed upgrade. 3 In practice this never happens as `WP_Scripts::localize()` is never called when `class.wp-scripts.php` is included from `wp-admin/load-scripts.php`. 4 5 Even if it did happen, this won't bring the site down. It will fail to output concatenated scripts or styles in the admin. Looking at the only report in the forum, this sounds more like a failed upgrade. Looking at