Tag Info

New answers tagged

0

Try (just change the names): add_action( 'init' , 'myyy_remove' , 15 ); function myyy_remove() { remove_action('ACTION_NAME', 'my_function_name_Something' ,11); remove_action('ACTION_NAME', 'my_function_name_Another' ,11); }


1

You have two options here In a child theme, dequeue and deregister the scripts and style you are not going to need. Just remember to hook your function to wp_enqueue_scripts with a lower priority (higher number) Use the twentyfifteen as a base to a new theme. I have successfully used bundled themes in the past to create new, selfstanding themes. That is ...


1

Check this codex page. In the event that a child theme is being used, the parent theme directory URI will be returned. So if you want to include your other css files you just need to all your CSS files: add_action( 'wp_enqueue_scripts', 'theme_enqueue_styles' ); function theme_enqueue_styles() { wp_enqueue_style( 'parent', ...


0

Child theme's can have their own header.php file, right? So why not just simply drop a child header.php file into the child theme's folder, then add the code there? Unless I'm missing something, this does seem to be the simplest solution.


0

I also just noticed the same error and it was due to me downloading the "Google Page Speed Insights" minified version of my style.css


0

I wrote a script called wp-diff you can use on the command line to implement the comparison step Brad Dalton mentioned. If you have many sites, a command line tool is far faster to use + can get to all your WordPress install files, with no requirement to change the Apache (or other server) config. Usually Web servers are configured to block access to .php ...


1

Twenty fourteen loads its stylesheets differently in that it made the main stylesheet dependant on the genericon stylesheet, and I'm sure that this is the problem you are experiencing. (if not, please update your question with proper details) You can change how you enqueue your style in the first block of code as follow wp_enqueue_style( 'parent-style', ...


0

I would expect that if you add a new filter with a higher priority it gets added to the existing color schemes: add_filter( 'twentyfifteen_color_schemes', 'wpse193782_custom_color_schemes', 99 ); function wpse193782_custom_color_schemes( $schemes ) { $schemes['default'] = array( 'label' => __( 'Colors by Kat', 'twentyfifteen' ), ...


0

This depends on how your parent theme hooks in the meta_boxes. If the callbacks are hooked to add_meta_boxes and written similar to the following from the Codex: function myplugin_add_meta_box() { $screens = array( 'post', 'page' ); foreach ( $screens as $screen ) { add_meta_box( 'myplugin_sectionid', __( 'My Post ...



Top 50 recent answers are included