I tried it and the exact same thing happened to me. Activating the child theme caused a 500 Internal Server error
and until I deleted both parent and child theme I could not get in either.
This is why I have a Crash Test Dummy installation and you’re not crazy. ??
It’s the F8 Lite functions.php
file that’s the culprit. It contains these two lines:
require_once ( get_stylesheet_directory() . '/theme-options.php' );
require_once ( get_stylesheet_directory() . '/images.php');
See that get_stylesheet_directory()
? That’s what’s making F8 Lite not child theme-able. If they are changed to these lines instead then the child theme will work.
require_once ( get_template_directory() . '/theme-options.php' );
require_once ( get_template_directory() . '/images.php');
Things that need to remain in the parent theme really need to use get_template_directory()
to work.
Recently Chip Bennett at WCGR gave a presentation on this very topic, it’s why I was able to figure it out.
Edit: For simple CSS only changes, give this plugin a look.
https://www.ads-software.com/extend/plugins/custom-css-manager-plugin/
If you do make those changes to the parent theme’s functions.php
file then if an update comes out your changes may be overwritten. by using that plugin (or one like it) then you can make those CSS changes but still get updates for that theme.