Generally speaking, Child Themes were originally intended to be able to do two things: Override parent Theme CSS Override parent Theme template files I doubt that the Theme developer intends for the /function-includes/theme-functions.php file to be overridden by a Child Theme. Functional files are usually a core component of the Theme, and allowing a Child … Read more
To clarify this, for anyone using Divi theme (but generally any WP theme), a simple inspection using Dev tools on the “head” for the stylesheet links usually gives a clue about the handle, as Den Isahac mentioned previously (it wasn’t clear as he mentioned it can’t be found). Anything before the “-css” on the ID … Read more
I try this code and it solve my problem if ( is_child_theme() === false ) { // files moved } else { // do nothing } Thankx to @birgire
I think I found a solution, but before a little Premise load_theme_textdomain() and load_child_theme_textdomain() are basically equal, the only difference is the default path they use: they get the current language (using get_locale()) and add the relative .mo file to the path passed as argument; then they call load_textdomain() passing as argument both the textdomain … Read more
Functions.php is shared for parent/child themes unlike other files which will be overridden. What that means is that WordPress will load both the parent and the child functions.php. In your case it sounds like you would simply create a child functions.php and then a create new register_sidebar . Then use dynamic_sidebar whenever you want in … Read more
Answer remade. The original was a wild idea… The solution is the same as the one posted by Rarst in the question linked How to *remove* a parent theme page template from a child theme? Difference being the admin_head hook. And a check for only running in edit-page and not in edit-post or edit-custom_post_type, as … Read more
The markup on the two sites is different. The main site, using your labels, has a body_class of left-sidebar, the network site as a body_class of right-sidebar. I’d call this a pure CSS/markup issue except that you are dealing with body_class so either there is a theme setting that did not transfer or something has … Read more
The child theme could just delete the parent theme file if it exists (via child theme functions.php). eg. $template = get_template_directory().’/woocommerce.php’; if (file_exists($template)) {unlink($template);} That would continue to override it if it came to exist again (ie. after a parent theme update.) If you aren’t going to update the parent theme just delete it’s woocommerce.php … Read more
It is pretty simple: function remove_nada_theme_font_style() { remove_action( ‘wp_enqueue_scripts’, ‘nada_theme_styles’ ); } add_action( ‘after_setup_theme’, ‘remove_nada_theme_font_style’ ); Since the child theme is loaded before the parent theme, you can’t simply remove the action. because the add_action calls in the parent theme will simply overwrite your requests. You have to wrap it into the after_setup_theme hook. This … Read more
Using an index.php in your Child Theme is optional; but having one will overwrite your Parent’s index.php. Using a blank index.php will also show you a blank page. You can copy the index.php from your Parent’s Theme to make it look like the Parent’s Theme, but there’s no need to do it. If there’s no … Read more