Regarding the "stray" header.png

Curiosity at some of the arguing about the stray header.png call that isn’t being found, and with it causing problems with some people’s websites, caused me to go digging. That, and I got a little upset about the attitude one user displayed over in the StudioPress forums about his problems with this while using Epik.

Anyway, I think I found what’s causing the problem.

Sure enough, all the Appfinite themes I have, Ally, Epik and Adapt, all have a line that creates a header.png call, easy enough to find when you do a view source:

<style type="text/css">.site-header { background: url(http://www.example.com/wp-content/themes/adapt/images/header.png) no-repeat !important; }</style>

But none of the Genesis 2.0 themes generate this, so I did some comparisons, and found what’s causing this difference.

In functions.php for the Appfinite themes I have, there’s this function:

// Add support for custom header
add_theme_support( 'genesis-custom-header', array(
	'width' => 360,
	'height' => 164
) );

but in the Genesis 2.0 themes like Magazine Pro, News Pro and the other HTML5 themes, that function call has been changed to this:

//* Add support for custom header
add_theme_support( 'custom-header', array(
        'header_image'    => '',
        'header-selector' => '.site-title a',
        'header-text'     => false,
        'height'          => 90,
        'width'           => 260,
) );

I did two tests… first test, I removed the genesis-custom-header call in Ally 1.3 completely, and that stray reference to a non-existent header.png disappeared. Second test, I changed the call to be just custom-header, and again, that header.png reference disappeared.

It also doesn’t seem to affect the ability to upload a custom header image in the admin area, so maybe this is a function that worked in Genesis 1.9 but was changed in 2.0 and now behaves differently, resulting in this header.png just crashing the party?

Just trying to help 🙂