Make WordPress Core

Changes between Version 1 and Version 2 of Ticket #28641, comment 2


Ignore:
Timestamp:
07/02/2014 04:51:42 PM (11 years ago)
Author:
McGuive7
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #28641, comment 2

    v1 v2  
    44
    55Unfortunately, this call to `wp_enqueue_media()` is part of the
    6 [Titan Framework(https://github.com/gambitph/Titan-Framework)], and is being enqueued somewhat indiscriminately. This may be an oversight, or it may just be technically challenging for the framework to know exactly when and where to add the enqueue across multiple, dynamically-generated options pages. Anyhow, not sure if I can expect the framework code to change anytime soon. . .
     6Titan Framework (https://github.com/gambitph/Titan-Framework), and is being enqueued somewhat indiscriminately. This may be an oversight, or it may just be technically challenging for the framework to know exactly when and where to add the enqueue across multiple, dynamically-generated options pages. Anyhow, not sure if I can expect the framework code to change anytime soon. . .
    77
    88I'd love to know if the issue is just that `wp_enqueue_media()` should not be called at all on the media library page, or if perhaps it's being called already on that page (although it seems like this should be an issue since the function checks if it's already been called, right? Something else entirely? I imagine there are probably lots of plugins calling `wp_enqueue_media()` across the board in the admin, and since this conflict only arises in WP 4.0 alpha, it seems like there are going to be lots of plugins causing the same issue. With all this in mind, is there a solution you'd suggest, either on the plugin/user end, or in WP core?