Yes, you can name a folder the new theme name. Move all the files to it. Put the new folder into the themes folder. Open style.css and on the first line, Theme Name: NewNameHere and save it.
Now when you go to themes in the dashboard, the new theme will be and won’t be overwritten during the upgrade process.
[Edit} But this won’t be a child theme per se. It will be it’s own stand alone theme.
yes, i see. I know my question was a bit condescending so to speak….as to why would anyone want to do this.
I simply do not understand the child theme process and it is confusing to me. I also don’t usually update a template once I get it to my liking (whether or not said creator updates the tempalte, etc.)
It almost seems less confusing to me, to edit a template to my liking, and then if they update something in the template that I may need or like, I can go to the one I renamed and place the code in the updated template.
I know that may seem odd, but I am simply trying to make it easier for what I understand, that is why I ask this question.
Maybe someone can advise me on a idiots guide to child template creation?
Another problem I have with the child template theory is I often edit in template images to my liking. I am not a coder, I am a graphics guy so coding is difficult for me, therefore it is easier to just create art within the template and leave all the naming the way it is.
I don’t even know how to go about implementing artwork in a true child template either.
Thanks for the help in answering the question, and I apologize in writing a book for a reply….it is just necessary for me to learn wordpress to a point and this child theme stuff is messing with me a bit. 🙂
The child theme confused me also and that is why I did it as above. I renamed the theme twenty11 and used a site search and replace to change every “twenty ten” to “twenty11”. So far no problems other than the site needs some css work to change some fonts, etc.
I did the same thing years back to the kubrick theme but I am updating those with the twenty11 theme as I heard the original kubrick theme might have problems with new browsers like FF4 and IE9.
I see, thanks for the information. At least I know I am no completely crazy. Maybe a little bit but not completely 🙂
What you’ve created is not a Child Theme, but rather a Derivative Theme.
The benefit of a Child Theme is that it doesn’t need to include every single template file, but only what is being modified from the Parent Theme.
At its simplest, a Child Theme can be nothing more than a
style.css, with an appropriate
Template:header tag. Such a Child Theme could completely reset the entire CSS, simply by not including the Parent Theme’s
style.css– or it could make iterative changes to the Parent Theme’s style, by doing an
@import('path/to/parent/theme/style.css'), and then any desired changes.
Slightly more complex, a Child Theme could also include a
functions.phpfile, with custom functions, filters, etc.
And slightly more complex, a Child Theme could also include any number of template files that are either new (such as additional page templates) or modified from the Parent Theme (such as a modified
By going this route, the Child Theme developer only has to maintain updates and changes to the few files in the Child Theme, while continuing to take advantage of continued development of the Parent Theme.
- The topic ‘Child theme creation’ is closed to new replies.