Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Copy the header.php file and paste it into your Child Theme folder. Then modify that.
Thread Starter
mdugre
(@mdugre)
Well, that’s easy enough BUT, in order to keep my modifications and my theme up to date, won’t I need to do this after each an every theme update?
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
If an update is done to a file, and that file is also in your child theme then you just manually add the changes
Thread Starter
mdugre
(@mdugre)
Huh? I think I’m missing something here. My understanding is that when there’s a theme update, potentially all files, including the header.php file, are modified.
If I copy the header.php file in my child theme directory, that file should also be modified, no? If this is indeed the case, that means that whatever modification is do will need to be re-entered. Is that not the case or I’m I missing something here?
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Well, you probably already know this but I’m just saying it to clarify, when you put a file in your Child Theme directory it doesn’t get modified in the process of an update, yes. But there is a compromise here, you don’t get the parent theme updates because you chose not to by including it into your Child Theme. If you want the parent theme updates then you just have to grab the actual code that was in the update, and put that code in your Child Theme header.php file.
Thread Starter
mdugre
(@mdugre)
And there in lie the problem. I want the updates to the parent theme reflected in the child theme.
In doing what you suggest, every time there’s an update to the theme, I’ll need to go in and copy paste the update code. I’m looking for a way around that
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Unless you’re using some sort of automated deployment tool, through a version control system like GIT, I don’t see how you’d get around that. It’s a fair compromise. But note that although every theme file is replaced in a theme update, not all theme files contain code changes.
I am not an expert by any means and others will be able to confirm this, but I think that you can have a header.php file in your child with only the changes you want leaving the main header.php file intact where it belongs, instead of copying the whole file to child.
Confirm this with d4z_c0nf or rdellconsulting
Read this about adding files to child theme. http://codex.wordpress.org/Child_Themes
And the answer is yes.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
I would have to leave a 5 star rating to Customizr if it really did that (waiting for confirmation lol)
According to the codex you can do it with any theme.
If you want to change more than just the stylesheet, your child theme can override any file in the parent theme: simply include a file of the same name in the child theme directory, and it will override the equivalent file in the parent theme directory when your site loads. For instance, if you want to change the PHP code for the site header, you can include a header.php in your child theme’s directory, and that file will be used instead of the parent theme’s header.php.
Thread Starter
mdugre
(@mdugre)
Thanks Andrew. Guess I’ll have to do some digging and maybe look at deployment tools\
Questas admin, appreciate the input but, if there’s a header.php file with the Customizr Child theme, I don’t see it
What I have on my screen when I select Customizr Child is the following
Templates
This child theme inherits templates from a parent theme, Customizr.
Theme Functions
(functions.php)
Styles
Stylesheet
(style.css)
You need to create the header.php file for your child and place it in your child directory.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
@questas_admin, Sorry I meant if it really did this:
but I think that you can have a header.php file in your child with only the changes you want leaving the main header.php file intact where it belongs, instead of copying the whole file to child.
