WordPress as a nice function is_active_widget that you can use in your __construct and test if the widget is present in the current page and add your scripts/styles based on that ex: function __construct() { parent::__construct(__CLASS__, ‘BasicWidget’, array( ‘classname’ => __CLASS__, ‘description’ => “This is a basic widget template that outputs text to the sidebar” … Read more
You are very nearer to the solution, because you are on the right path. Just to tweak a little bit: There are two such action hooks: wp_print_scripts, and wp_print_styles So the way you can do it, is: hook ’em differently: //Dequeue Styles function project_dequeue_unnecessary_styles() { wp_dequeue_style( ‘bootstrap-map’ ); wp_deregister_style( ‘bootstrap-map’ ); } add_action( ‘wp_print_styles’, ‘project_dequeue_unnecessary_styles’ … Read more
do_action doesn’t quite work like that. When you call do_action(‘crunchify_print_scripts_styles’) WP looks at its list of registered actions and filters for any that are attached to a hook called crunchify_print_scripts_styles and then runs those functions. And you probably want to remove this: add_action( ‘wp_enqueue_scripts’, ‘crunchify_print_scripts_styles’); … because you aren’t able to get the return result … Read more
the $wp_scripts global holds all the script data: function wpa54064_inspect_scripts() { global $wp_scripts; foreach( $wp_scripts->queue as $handle ) : echo $handle; endforeach; } add_action( ‘wp_print_scripts’, ‘wpa54064_inspect_scripts’ );
I for myself use a combination of: one file dedicated to the one-time script using a transient to stop the script from accidentally running more than once using capability-management or user-control to ensure the script is just run by me. Structure I use a file (onetime.php) in my include-folder inc, which is included in the … Read more