Using wp_deregister_style( ‘login’ ) to remove the login styles will still result in a 404’d request for the login CSS file. However, if you re-register the login style after deregistering it you can prevent the unwanted request. add_action( ‘login_init’, function() { wp_deregister_style( ‘login’ ); wp_register_style( ‘login’ ); } ); This will leave you with a … Read more
widget() method is called when widget is rendered, so the style you’re enqueuing are printed in the footer (header is already printed at that time). Even if majority of browser can render styles linked from page body, that’s invalid HTML because, according to HTML standards, unlike scrypts, styles must be placed in page <head>. (Try … Read more
Note: the file name is functions.php, not function.php (but that’s probably just a typo in the question). To remove a script or style, you must remove it after it was added. If you try to remove it before it was added, or even print $GLOBALS[‘wp_scripts’]->registered, nothing will happen, since it was not added yet. So … Read more
You are using plugins_url – therefore pointing to completly different directory than your current theme. If you are just trying to enqueue a theme style do it like this: function load_theme_styles() { wp_enqueue_style(‘main-css’, get_template_directory_uri() . ‘/style.css’, array(), ‘1.0’, ‘all’); } add_action(‘wp_enqueue_scripts’, ‘load_theme_styles’); the wp_enqueue_style takes some parameters. In the example above I am using: A … Read more
Yes and no. You can load a raw CSS string into the header programatically, but you can’t use wp_enqueue_style() to enqueue it. That function specifically loads files into the header in <link> tags. But what you can do is something like this: function print_inline_script() { ?> <style type=”text/css”> /* … styles go here … */ … Read more
I think you could get around this by pre-running the shortcodes on the page by applying the content filters before the header is output. This should allow any internal shortcodes run inside the included post to add any action hooks properly and thus any needed stylesheets/resources. add_action(‘wp_loaded’,’maybe_prerun_shortcodes’); function maybe_prerun_shortcodes() { if (is_page()) { global $post; … Read more
Remove styles added with wp_add_inline_style() If we want to keep the custom-style-css but only remove the custom-style-inline-css, then we can try e.g. add_action( ‘wp_print_styles’, function() { // Remove previous inline style wp_styles()->add_data( ‘custom-style’, ‘after’, ” ); } ); where after is data key for the inline style corresponding to the custom-style handler. There is exists … Read more
To answer your first question, you would use the second style, i.e. function add_my_stylesheet() { wp_enqueue_style( ‘myCSS’, plugins_url( ‘/css/myCSS.css’, __FILE__ ) ); wp_enqueue_style( ‘myCSS1’, plugins_url( ‘/css/myCSS1.css’, __FILE__ ) ); } add_action(‘admin_print_styles’, ‘add_my_stylesheet’); What the add_action() function does is tell WordPress, “When the admin_print_styles action occurs, run this add_my_stylesheet() function.” Confusingly, the practice of using the … Read more
This is not possible the way you think. It would maybe be possible if you use Reflections or debug_backtrace(), but there’s no reliable way to do this. WordPress does not keep a stack or queue where it tracks file names. The only thing I could imagine is just hooking into the action and inside wp_enqueue_scripts(): … Read more
Okay, here’s where I’m at with a solution. wp_enqueue_style( ‘my-handle’, ‘mystyle.css’ ); global $wp_styles; $wp_styles->add_data( ‘my-handle’, ‘title’, ‘my_stylesheet_title’ ); Don’t like using the global. Is there something better?