Creating child themes is pretty easy. What you do is go to the theme directory, and create a folder named zeeminty-child. What you do then is create a file called style.css in that folder and paste the following at the top of the file:
/*
Theme Name: Zeeminty Child
*/
@import url("../zeeminty/style.css");
You can then add copies of all the files you want to edit to this folder, template files will overwrite those in the parent theme automatically. It’s really a necessary evil, since all the changes you make to the parent theme will be overwritten when you update the theme (which you don’t want).
That said, why not just go to your page and use the fullwidth template?
thanks very much for your help. Managed to create the child theme and learnt how to set up fullwidth template which has solved the problem.
Hi, I have been following the instructions for a child theme of zeeminty but even with the @import code like shown above I still have an unstyled page. I tried using the Child Themify plugin with the same result. Any ideas?
This is what I have
/*
Theme Name: zeeMinty Child
Theme URI: http://theatreact.net.au/zeeminty-child/
Description: zeeMinty Child Theme
Author: Gavin Findlay
Author URI: http://theatreact.net.au/
Template: zeeminty
Version: 1.0.0
Tags: black, blue, custom-background, custom-colors, custom-header, custom-menu, editor-style, featured-image-header, featured-images, flexible-header, full-width-template, gray, green, left sidebar, light, one-column, orange, purple, red, right sidebar, silver, sticky-post, theme-options, threaded-comments, three columns, translation-ready, two columns, white
Text Domain: zeeminty-child
*/
@import url(“../zeeminty/style.css”);
/* =Theme customization starts here
————————————————————– */
Is your child theme file located in it’s own folder in the theme directory named, “zeeminty-child”? Also, is the original style.css in the root level of the zeeminty folder? If so, does it have anything in it?
If you check everything above and nothing is working, I would turn error reporting on by going into your wp-config.php file and making sure the following line reads as follow:
define('WP_DEBUG', true);
After this, reload your page, and see if the problem isn’t some coding error.
