Of course right after I post this, I find an answer…so hopefully someone else can benefit from this. For me, the answer was instead of unregistering nav menu items, I needed to just remove the action…so my function now looks like this: function remove_cornerstone_menus() { remove_action(‘init’, ‘cornerstone_menus’); } add_action(‘init’, ‘remove_cornerstone_menus’); Worked like a charm.
Is this even possible? If your description is correct and … The function is not pluggable, by which I assume you mean not wrapped in a if (!function_exists()) condition and The function is not a callback for an action or a filter and The function is not in a theme file that gets automatically substituted … Read more
As you mentioned, a child theme is designed exactly for the purpose of not losing your changes upon updating the parent theme. Updating the child theme is not always mandatory, however there might be cases that you should do so. Consider this: You update the parent, and the update removes some of core functions, which … Read more
You simply need to run your code on a higher priority than what the parent theme is, the default on add_action function is 10 so you can use: function s157343_unregister_widgets() { unregister_widget( ‘Chocolat_Widget_New_Entrys’ ); } add_action( ‘widgets_init’, ‘s157343_unregister_widgets’, 20 ); This will unregister that widget. Of course, you can still create a new class that … Read more
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
You can’t necessarily replace entire arbitrary files with a child theme. WordPress will automatically look in the child theme for replacements for the templates in the template hierarchy, as well as a couple of additional files like searchform.php or comments.php, but any other files that the parent theme loads are only replaceable in a child … 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 are overthinking this. The namespace structure applies at the level of individual package. There is no need or push to treat the whole site as such package. Also one of the benefits of using autoload in first place is that it makes location of classes in file system largely irrelevant. So the simple and … 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