Archived topic
Child theme broken
14 replies · Started by Michael on January 20, 2022
Don't know when this error started, but it's in my themes area
Broken Themes
The following themes are installed but incomplete.
Name Description
generatepress_child Template is missing. Standalone themes need to have a index.php template file. Child themes need to have a Template header in the style.css stylesheet.
So, I downloaded the child theme from here, installed it. Same error ? Added my custom CSS and some other files (unrelated) ie back to how it was, still not working. Switched to the main GP theme to see if I got the same error. Didn't, but now I can't switch back to the child theme because of it being "Broken"
Hi there,
That sounds strange.
So the issue exists when you download a fresh copy from here?
https://docs.generatepress.com/article/using-child-theme/
Hi Leo,
Yes it is strange, and yes when I download a fresh copy from here and install it, I can't see an index.php file in there, just functions.php an image and a stylesheet.
index.php isn't a requirement for the child theme.
Does that file still exist in your parent theme?
https://github.com/tomusborne/generatepress
I agree index.php isn't a requirement, so am not sure what is displaying this error, or why. The index.php exists in the parent theme yes. Am not sure what that means also about the template header in the style sheet?
The parent is the only one active, so I've lost my customisations until I can resolve really.
Hi there,
has there been any changes made to the parent GeneratePress theme?
Hi,
No, none at all. I do all my changes on the child theme.
I wonder if theres an issue with the parent theme - maybe something got corrupted.
Could you try re-installing the parent theme from a new download ?
Really can't recall seeing this issue before.
Can you create a staging site and provide the access to us to take a look?
Leo, apologies for the delay. Staging site isn't an option unfortunately, still the same thing showing in the theme area. Be more than willing to send login details for you to take a look at why this is happening.
I'm not sure how we can do some debugging and testing without a staging site.
Please keep in mind that we have no other reports on this so it's likely something specific to your install.
It more than likely is, tracking it isn't easy. Not to worry, it's not broken anything.
Sounds good.
We can take a look whenever a staging site can be set up.
Hopefully in the not too distant future, I tried a few weeks ago, but the migration broke a lot of things, so reverted back.
