If you don’t want to develop/maintain your own Theme, then yes: choose an existing Theme, and make modifications to it via Child Theme. If, on the other hand, you are comfortable with developing/maintaining your own Theme, then either create a new Theme, or make a derivative of an existing Theme. Since, as you state, you … Read more
Not using the current system. In order to serve as a valid Template for a Child Theme, the Parent Theme must exist, and be a valid Theme. That’s because the Parent Theme’s template files must be accessible via locate_template(), in order for the Child-Parent fallback to work properly. Note: if this core Trac ticket is … Read more
Why exactly are you trying to redeclare that function? You can either edit the original function, or, better yet, use remove_action to remove add_action( ‘widgets_init’, ‘twentyeleven_widgets_init’ ); and then reattach your own function add_action(‘widgets_init’, ‘your_widgets_init_function’ );
WordPress use an option to store the current active child theme. This option is named ‘stylesheet’. Using the filter ‘pre_option_{$option_name}’ you can change every option getted by WP. So, in your case you should hook the ‘pre_option_stylesheet’ filter, use some logic to retrieve current season and return the child theme you want. This workflow should … Read more
Create index.php and format it the way you want. Then create page.php and load the index file with something very simple like: get_template_part(‘index’): Note: This is untested and I am not able to test this right now. If there is a problem, leave a comment and I will run proper testing later and get back … Read more
I think your problem is how your function is constructed and not your condition as such. You should not be wrapping your function and your action in a condition like this. Page templates are selected really late in the query by the main query, and I probably think that this is way to late for … Read more
Actually, what you have described is the correct way to do things and there shouldn’t be any noticeable impact on site speed and performance. Using child themes also has the benefit of allowing your changes to persist through theme upgrades.
Well, this is what worked for me. In my functions.php file I put the following code: function header_widgets_init() { register_sidebar( array( ‘name’ => ‘Header Sidebar’, ‘id’ => ‘header_sidebar’, ‘before_widget’ => ‘<aside class=”widget %2$s”>’, ‘after_widget’ => ‘</aside>’, ‘before_title’ => ‘<h2 class=”widget-title”>’, ‘after_title’ => ‘</h2>’, ) ); } add_action( ‘widgets_init’, ‘header_widgets_init’ ); …and in my header.php file … Read more
There’s no need for the wp-content/themes path – both themes sit in the same directory, so you can just traverse up one and then back down to child theme: background-image: url(../child-theme-name/images/some-image.png); Update: Regarding your answer to “where is the CSS file stored”, you inferred that the stylesheet resides in the child theme folder – in … Read more
You are missing part of the boilerplate needed in the comments area at the top of the stylesheet file. You need a line that says: Template: [name of parent theme folder] For example if the folder in the /wp-content/themes folder for the parent theme is integrative-wisdom you would have: /*! Theme Name: Integrative Wisdom Child … Read more