Think of WordPress execution as a series of rungs on a ladder: WordPress climbs one rung, then the next, then the next, and so on. Think of action hooks as the rungs themselves. Here is a (slightly abbreviated, I think) list of those actions, or “rungs” executed during a typical WordPress request. Thus, an add_action() … Read more
If the desired functions are in the parent theme’s functions.php then you can include them in your currently executing child theme functions.php with this call: include( get_template_directory() . ‘/functions.php’); get_template_directory() finds the parent’s directory even when using a child theme. Note that this will run everything found to be executable in the parent theme’s functions.php. … Read more
You can try this. add_action( ‘wp_enqueue_scripts’, ‘wpcustom_enqueue_script’ ); function wpcustom_enqueue_script() { wp_enqueue_style( ‘datepicker-style’, ‘https://code.jquery.com/ui/1.12.1/themes/base/jquery-ui.css’ ); wp_enqueue_script( ‘js-datepicker’, ‘https://code.jquery.com/ui/1.12.1/jquery-ui.js’, array(‘jquery’), null, true); } Readmore: http://jqueryui.com/datepicker/
You can try to detect if the current used theme is a child and if so pointing the inline CSS to the right style. I didn’t tested this solution but could be a good starting point. function mytheme_enqueue_style() { wp_enqueue_style( ‘parent-theme-style’,get_template_directory_uri() . ‘/style.css’, false ); if(is_child_theme()) { wp_enqueue_style( ‘child-theme-style’, get_stylesheet_directory_uri() . ‘/style.css’, array(‘parent-theme-style’) ); } … Read more
I’m not familiar with Gutenberg, but as you mentioned it as an example, I assume you didn’t mean “only” Gutenberg. The wp_enqeue_script() or wp_enqueue_style() functions do not accept arguments regarding posts or pages. The script are registered and rendered globally. If a script is output on certain posts only, then it has to be a … Read more
If wp_add_inline_css is fired within an action you can use remove_action with the same parameters. You also might use wp_enqueue_scripts action to dequeue any scripts or styles in a proper way. But, inline style are not included in the $wp_styles global, you can unset them with the action print_styles_array, you need to know the handle … Read more
Naming conventions for scripts and styles have always been a difficult issue in WordPress plugins, with many different conventions used and often causing conflicts. I’ll try to give my view on this matter, and elaborate where necessary. Let me start off by stating my opinion on the example in your question: in my opinion, only … Read more
The bug’s only 4 years old so you wouldn’t want to rush them would you?! A workaround is to leave out the wp_style_add_data() and use the ‘style_loader_tag’ filter: add_filter( ‘style_loader_tag’, function ( $tag, $handle ) { if ( $handle == ‘purecss-all-not-ie’ ) { $tag = “<!–[if gt IE 8]><!–>\n” . $tag . “<!–<![endif]–>\n”; } return … Read more
In short, as of WordPress 3.3 use wp_enqueue_scripts to load JS and CSS. wp_print_styles has/had some minor bugs with it (namely, it may include your scripts in the admin as well) – here and here are some more details on all of that. It doesn’t sound like there’s any major security flaws or theme breaking … Read more
My error. All I had to do was knock off the -css and it worked. Working code: <?php function dequeue_dequeue_plugin_style(){ wp_dequeue_style( ‘plugin’ ); //Name of Style ID. } add_action( ‘wp_enqueue_scripts’, ‘dequeue_dequeue_plugin_style’, 999 ); ?>