How Do I Create Child Theme (Plain Language, Please)

Here you go –

https://codex.www.ads-software.com/Child_Themes

You will have to redo various theme settings as they don’t carry over from a parent theme.

I’m prepared for the work as long as I know how to do it. ??
I appreciate the link, however there’s much in there I do not understand.

Things like: “The next step is to create your child theme’s stylesheet (style.css). The stylesheet must begin with the following (the stylesheet header):”

I don’t know what that is, where to find it or how to change it.

Also, “The final step is to enqueue the parent and child theme stylesheets.”
I don’t know that, either. I really do need a detailed how-to with plain language. I fell into this website thing almost by accident and I am learning as I go. But I’m far from understanding these directions.

Here’s a video that has more explanations –

https://www.wpbeginner.com/wp-themes/how-to-create-a-wordpress-child-theme-video/

But there is one piece in there that is no longer current – the part about using the @import line in the style.css file.

BUT, I just looked at the theme description and it says this:

Easily add a logo to your site and create a beautiful homepage using the built-in homepage layout.

Have you checked to see if that will work for you?

Also, it’s best to use the sub-forum specific to the theme you are using, so I’d also suggest that if you need more help on this, that you start a new thread here – the developers and other people familiar with the theme will see it there:

https://www.ads-software.com/support/theme/minamaze#postform

…there is one piece in there that is no longer current – the part about using the @import line in the style.css file.

If I may ask, where can I learn about that?

Thank you, WPyogi- I’m searching around to see if I can find it. (The easily add logo part). Crossing my fingers it’s that easy!

And oh my gosh it is that easy. a simple checkbox on the Theme Options / General settings page.

I’m off to celebrate!! Thank you!!

This is my favorite method for creating a Child Theme. I believe it adds the style import line.

https://www.ads-software.com/plugins/one-click-child-theme/

Great for you there, YoMommaIII!

@ Radices: My own Twenty Twelve Child Theme does *not* use @import, but I used to have that in there and this is the first I have heard of that line no longer being current. @import certainly is (or can be) quite convenient, yet it does slow things down just a bit.

Re: using @import, please see:

The final step is to enqueue the parent and child theme stylesheets. Note that the previous method was to import the parent theme stylesheet using @import: this is no longer best practice. The correct method of enqueuing the parent theme stylesheet is to use wp_enqueue_script() in your child theme’s functions.php. You will therefore need to create a functions.php in your child theme directory. The first line of your child theme’s functions.php will be an opening PHP tag (<?php), after which you can enqueue your parent and child theme stylesheets with the following function (setting ‘parent-style’ as a dependency will ensure that the child theme stylesheet loads after it):

From the Codex – https://codex.www.ads-software.com/Child_Themes

I’m changing all my sites to use the newer method to enqueue the styles. I understand the @import would break some plugins/sites using JS / Jquery.

@leejosepho

Seems that it’s not as simple as the Codex says. If the parent theme uses more than one .CSS file and is enqueue-ing them then the “NEW” method will break the dependancies.

Check the last post in this thread. I’m using it on a couple of sites. Seems like a lot to save 200MS load time:)

https://wordpress.stackexchange.com/questions/163301/versioning-import-of-parent-themes-style-css

Seems that it’s not as simple as the Codex says.

Understood, and as you would know, the link you posted offers a very-informative read that includes suggestions even from Oscar.
https://wordpress.stackexchange.com/questions/163301/versioning-import-of-parent-themes-style-css

I think one of the various challenges with the Codex is to understand not all pages are comprehensive, and certainly not always within the reader’s context-of-thought. However, neither would it be practical or truly useful to include mention of every facet or nuance on every page unless every reader is prepared either to learn or to sift through all the kinds of fine details continually rolling around in the brains of deep coders.