[wp-trac] [WordPress Trac] #20513: Refactor $wp_scripts init checking code
WordPress Trac
wp-trac at lists.automattic.com
Mon Apr 23 12:39:16 UTC 2012
#20513: Refactor $wp_scripts init checking code
-------------------------------------+------------------------------
Reporter: GaryJ | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version: 3.4
Severity: normal | Resolution:
Keywords: has-patch needs-testing |
-------------------------------------+------------------------------
Comment (by GaryJ):
Related discussion: #11526.
How expensive is `debug_backtrace( false )`?
How many themes and plugins are still firing these functions before `init`
action has occurred? (Nacin's relatively recent post might have reminded
some of the authors to be using the `wp_enqueue_scripts` hook.)
Could `wp_debug_backtrace_summary()` be used to pinpoint the original
function called?
While scribu's suggestion may well work, it seems dirty to be including an
argument purely for debugging purposes.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/20513#comment:10>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list