Viewing 8 replies - 1 through 8 (of 8 total)
  • Hi there,

    yes the issue is you have no template header in the child theme.

    If you edit the Child Themes stylesheet it should have this at the very top:

    /*
     Theme Name:   GeneratePress Child
     Theme URI:    https://generatepress.com
     Description:  Default GeneratePress child theme
     Author:       Tom Usborne
     Author URI:   https://tomusborne.com
     Template:     generatepress
     Version:      0.1
    */

    You can change that header BUT you must leave this line as is:

    Template:     generatepress

    Without it WordPress will not know that GeneratePress is the parent.

    Thread Starter jhmaths

    (@jhmaths)

    Thank you David. I’m a bit nervous about this now as I’m not very experienced with this sort of thing. So are you saying that if I copy and paste that header and put it at the very top of the styles.css file in my child theme folder then that will resolve this issue?

    How did this issue arise? Is this something that’s supposed to be done when creating a child theme?

    Thanks.

    By default the GP Child Theme has that header included… so if you used the one we provided in this doc then it should be there:
    https://docs.generatepress.com/article/using-child-theme/

    If you edit your child theme and look at the styles.css what do you currently see there?

    Thread Starter jhmaths

    (@jhmaths)

    /*
    
    Theme Name: GeneratePress
    
    Theme URI: https://generatepress.com
    
    Author: Tom Usborne
    
    Author URI: https://tomusborne.com
    
    Description: GeneratePress is a lightweight WordPress theme built with a focus on speed and usability. Performance is important to us, which is why a fresh GeneratePress install adds less than 10kb (gzipped) to your page size. We take full advantage of the block editor (Gutenberg), which gives you more control over creating your content. If you use page builders, GeneratePress is the right theme for you. It is completely compatible with all major page builders, including Beaver Builder and Elementor. Thanks to our emphasis on WordPress coding standards, we can boast full compatibility with all well-coded plugins, including WooCommerce. GeneratePress is fully responsive, uses valid HTML/CSS, and is translated into over 25 languages by our amazing community of users. A few of our many features include 60+ color controls, powerful dynamic typography, 5 navigation locations, 5 sidebar layouts, dropdown menus (click or hover), and 9 widget areas. Learn more and check out our powerful premium version at https://generatepress.com
    
    Version: 3.3.1
    
    Requires at least: 5.2
    
    Tested up to: 6.3
    
    Requires PHP: 5.6
    
    License: GNU General Public License v2 or later
    
    License URI: https://www.gnu.org/licenses/gpl-2.0.html
    
    Text Domain: generatepress
    
    Tags: two-columns, three-columns, one-column, right-sidebar, left-sidebar, footer-widgets, blog, e-commerce, flexible-header, full-width-template, buddypress, custom-header, custom-background, custom-menu, custom-colors, sticky-post, threaded-comments, translation-ready, rtl-language-support, featured-images, theme-options
    
    GeneratePress, Copyright 2014-2023 EDGE22 Studios LTD.
    
    GeneratePress is distributed under the terms of the GNU GPL
    
    GeneratePress is based on Underscores https://underscores.me/, (C) 2012-2022 Automattic, Inc.
    
    Actual CSS can be found in /assets/css/ folder.
    
    */
    Thread Starter jhmaths

    (@jhmaths)

    This is in both GP and GP child styles.css

    Then thats not correct for the Child Theme.
    It should have the header i shared here:

    https://www.ads-software.com/support/topic/broken-child-theme-message/#post-17191273

    Thread Starter jhmaths

    (@jhmaths)

    It’s not showing as broken anymore, thanks again for your help David.

    You’re welcome

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Broken child theme message’ is closed to new replies.