front-end.css not loaded in public site

[bugsysop]

If I change this declaration in functions.php of my child theme:

// Defines the child theme (do not remove).
define( 'CHILD_THEME_NAME', 'Genesis Sample' );
define( 'CHILD_THEME_URL', 'https://www.studiopress.com/' );
define( 'CHILD_THEME_VERSION', '2.7.0' );

to

// Defines the child theme (do not remove).
define( 'CHILD_THEME_NAME', 'My Theme' );
define( 'CHILD_THEME_URL', 'https://www.studiopress.com/' );
define( 'CHILD_THEME_VERSION', '1.0' );

The front-end.css file for Gutenberg is not loaded anymore in site header

[nickcernis]

Thank you for this report, @bugsysop.

This is because the front-end.css file depends on the genesis-sample stylesheet by name here:

genesis-sample/lib/gutenberg/init.php

Lines 19 to 24 in 6801a3f

	wp_enqueue_style(
	'genesis-sample-gutenberg',
	get_stylesheet_directory_uri() . '/lib/gutenberg/front-end.css',
	array( 'genesis-sample' ),
	CHILD_THEME_VERSION
	);

If you rename your theme, it's best to also rename all genesis_sample and genesis-sample strings to match your new theme name in the code (to my_theme and my-theme), which will prevent issues like this one.

I'll leave this open to look into ways to prevent the need for this, though. We could either:

• Create an npm script or mini site to make theme renaming easier.
• Pull the child theme name from the constant automatically and use that in the dependency, instead of hard-coding genesis-sample.

[nickcernis]

Resolved in 69c3f36. The CHILD_THEME_NAME will now be used for the dependency automatically.

I also opened #142 to add the ability to rename the theme more easily via an npm script or mini site.

[nathanrice]

Resolved in 69c3f36. The CHILD_THEME_NAME will now be used for the dependency automatically.

💯