Okay so i did manage to add some custom css selectively on pages that load the medialement player by adding this to my functions.php file: function custom_player() { wp_enqueue_style( ‘custom-player’, get_stylesheet_directory_uri() . ‘/wp-mediaelement.css’ ); $custom_css = ” /*here goes the css*/ “; wp_add_inline_style( ‘custom-player’, $custom_css ); } add_action( ‘wp_enqueue_scripts’, ‘custom_player’ ); Like this by using … Read more
get_template_directory_uri always returns the parent theme’s URI. From the docs: In the event a child theme is being used, the parent theme directory URI will be returned You probably want get_stylesheet_directory_uri. add_action(‘wp_enqueue_scripts’, ‘wpse174502_styles’, PHP_INT_MAX); function wpse174502_styles() { wp_enqueue_script(‘bootstrap-js’, get_stylesheet_directory_uri().’/bootstrap/js/bootstrap.min.js’, array(‘jquery’), NULL, true); wp_enqueue_style(‘bootstrap-css’, get_stylesheet_directory_uri().’/bootstrap/css/bootstrap.min.css’, false, NULL, ‘all’); } Whenever you’re debugging enqueues be sure to… … Read more
Those classes are output by the body_class function, which can be filtered by plugins to add their own classes. You don’t need to (and shouldn’t) harcode classes into the body tag in your template, just add that function within the body tag: <body <?php body_class(); ?>>
The problem is not there in your @font-face it’s actually in the functions.php where you enqueued the stylesheets. What I assume your parent theme is enqueuing stylesheets like below: <link rel=”stylesheet” id=’bootstrap-css’ href=”http://example.com/wp-content/themes/parenttheme/bootstrap.min.css” type=”text/css” media=”all” /> <link rel=”stylesheet” id=’style-css’ href=”http://example.com/wp-content/themes/parenttheme/style.css” type=”text/css” media=”all” /> But what’s happening in your child theme: <link rel=”stylesheet” id=’parent-style-css’ href=”http://example.com/wp-content/themes/parenttheme/style.css” type=”text/css” … Read more
I am guessing a lot about how your themes work but, the child theme’s functions.php runs before the parent theme’s functions.php, so anything loaded by the parent’s functions isn’t going to be present for you to remove. You need to hook your function so that it runs later. add_action(‘after_setup_theme’, ‘remove_custom’); Though you would need to … Read more
WordPress parent theme are the main file which contains all data and coding. If you directly edit everything in the parent theme such as CSS, functions and any other pages then it might be possible to lose many of previously made changes when you will update to new version of that theme. So, it is … Read more
I think that the error message is clear enough: the class was not found. The first thing you should do is to verify the path you are using to load the file where the class is defined. If you do that and check the value of child_template_directory constant, you will see that it has not … Read more
It really just depends on what you need to do here. The general method is to hook all your theme support features to after_setup_theme for some obvious reasons. after_setup_theme is the first action hook available to themes to add any type of support the theme. Certain features has to be registered here and cannot be … Read more
You will need to find how your theme is calling the styles. If with enqueue, you can use the wp_dequeue_style() on your child theme, if directly in header/footer, you will need to copy those to your child theme and remove those calls.
You can add a filter to page_link to modify link output: function wpd_add_fragment_to_pages( $url ) { return $url . ‘#navbar’; } add_filter( ‘page_link’, ‘wpd_add_fragment_to_pages’ );