It depends entirely on a) what functions and template files you’re talking about, and b) how those functions are defined, or template files are called, in the Parent Theme. If the Parent Theme uses get_template_part(), then you’re golden. If the Parent Theme uses get_stylesheet_directory_uri() or STYLESHEETPATH, then you can override, with caveats. If the Parent … Read more
As One Trick Pony said, there’s a dedicated function (since WP 3.0): is_child_theme()
you may use this below code for your problem: [1]: https://i.stack.imgur.com/5aX1D.png or use below code: add_action( ‘after_setup_theme’, function () { load_theme_textdomain( ‘your parent theme name’, get_stylesheet_directory() . ‘/languages/’ ); load_child_theme_textdomain( ‘your child theme name’, get_stylesheet_directory() . ‘/languages’ ); } );
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
Why not use a completely separate repo for each child-theme site once its established? Clone the master repo when spinning up the environment, remove the Git directory, init a new Git repo, and push it up to wherever? Now each child theme can be developed independently of each other. Alternatively, if you’re using the same … Read more
There are three core principles to parent/child theme logic in WordPress: functions.php files from both parent and child get executed during load, with the child one first (this is a little counter-intuitive so worth remembering). “Template directory” refers to parent theme and “stylesheet directory” refers to child theme. If no child theme is being used … Read more
I am never sure about ‘optimal approach’ – however, I am using this in the functions.php in a child theme of Twenty Eleven //deregister the header images of Twenty Eleven, and register a few new RAW header images// add_action( ‘after_setup_theme’, ‘raw_theme_header_images’, 11 ); function raw_theme_header_images() { unregister_default_headers( array( ‘wheel’, ‘shore’, ‘trolley’, ‘pine-cone’, ‘chessboard’, ‘lanterns’, ‘willow’, … Read more
In the WP_Theme class, the get method gives you a sanitized theme header. You cannot use it to extract a property. Actually you don’t need to, as you can access it directly like this: // get the parent object $parent = wp_get_theme()->parent(); // get parent version if (!empty($parent)) $parent_version = $parent->Version;
Thanks for all the help which pointed me in the right direction. In the end I used the following: $style_parent_theme = wp_get_theme(get_template()); $style_parent_theme_author = $style_parent_theme->get( ‘Author’ ); I use get_template() to recover the folder name of the parent theme. wp_get_theme then get’s the theme object. Once we have that we can manipulate the object to … Read more
One does not simply throw <link> (CSS) or <script> tags into the <head> of a WordPress theme. The right way to do it: Register, enqueue … tadaa! WordPress has the “Dependency API” for this task. It consists basically out of those public functions: wp_register_script() wp_enqueue_script() wp_register_style() wp_enqueue_style() Then there’re aligning functions to deregister scripts or … Read more