@troy You’re right that none of these files can be overridden by placing modified versions in your child theme. However, this needn’t prevent you from implementing your modifications.
templatetags.php to implement Boone’s fix of the xprofile group tabs on the front-end edit screen. This one will be fixed in the next version, so I’m not so worried about it.
There’s no need to override this file – go ahead and modify the file in the ‘cbox-theme’ parent theme directory. It’ll be overwritten with the fixed version in the next update.
in cbox theme documentation there is a wireframe of the home page template that identifies a “free text area” just beneath the slider. It doesn’t seem to exist in the current template.
Apologies – this is indeed a mistake in the documentation.
In any event, I want to put a widget there anyway. So I’m using sidebars-cbox.php to define a new widget are to call from a modified homepage-template. The child homepage-template overrides the parent, but the sidebars-cbox.php does not. Such a change in the parent theme would not be future proof.
You don’t need to override sidebars-cbox.php to achieve this. The slightly-misnamed “sidebars” (actually widget areas, as you’ve discovered) are registered cumulatively. All you’d need to do is to register your sidebar in addition to the existing ones. So, in your child theme’s functions.php file, add the following and amend to suit your needs:
/**
* Register even more sidebars.
*/
function cbox_child_theme_register_sidebars() {
register_sidebar( array(
'name' => 'Homepage Free',
'id' => 'homepage-free',
'description' => "The free text Widget on the Homepage",
'before_widget' => '<div id="%1$s" class="widget %2$s">',
'after_widget' => '</div>',
'before_title' => '<h4>',
'after_title' => '</h4>'
));
}
add_action( 'widgets_init', 'cbox_child_theme_register_sidebars' );
Hope that helps.
Cheers, Christian
.
