jiraiya

Hey sorry about the late reply. I ended up very busy for a few days and the post slipped my mind. Also for some reason I have not been getting notified by email of replies. Yeah you have pretty much confirmed my fears on this one. I had thought as much myself. It’s a pity that it works this way since it really screws with the way child themes are supposed to work in my view. Is there a way to disable the customiser for a child theme altogether?

Thanks,
Barry.

Hi dains,
I read your post today. I hope the solution fixed your problem. If you run into any more difficulties you can post here again and I’d be happy to help.

Cheers,
You were correct and got me on the right track. I solved it and posted the solution
here.

Sorted this one guys. Not so much a bug as just a behavourial difference between TwentyTen and wordpress core. If you do as I posted initially the confusing behavior does indeed exist, no doubt. To solve it you need to override a function. The TwentyTen theme was specifying that a home page of my posts be displayed. However if you turn it to a static page in the options then the static home page is indeed displayed but it seems to throw things out of sync with the wordpress core and the drop downs wont work. The solution is as follows. Remove the filter which adds the home page. Then they play nice together. Hope it helps someone else.

<?php
/* Perform some setup on the child theme */
add_action( 'after_setup_theme', 'child_theme_setup' );

function child_theme_setup() {
/* We don't want to display a default home page. */
remove_filter( 'wp_page_menu_args', 'twentyten_page_menu_args' );

/*Add a new menu location*/
register_nav_menus(
    array('left-sub-menu' => __( 'Left Sub Menu' ) )
  );
}

?>