How can I remove “featured post” header?

The featured post is an integral part of the theme. Short term, you can how the pages would look without it by editing style.css (line 40) and changing:

.postwrap {
margin:auto;
padding:30px 0 40px;
width:974px;
}

to

.postwrap {
display:none;
margin:auto;
padding:30px 0 40px;
width:974px;
}

Longer term, I think you’d need to edit the index.php, single.php, category.php and archive.php files in your theme.

It works!!! Thanks.

But why would I want to change it in the other php files if this works? Will there be a problem???

Btw: This is the change I made:

.postwrap{width:974px; margin:auto; padding:30px 0 40px 0;}

to
.postwrap{display:none;width:974px; margin:auto; padding:30px 0 40px 0;}

Do you have any idea how to fix this error below??? I installed and activated the Gravatar plugin (I’ve tried a few actually), but still get the error on pages where people comment using a gravatar:

<img src=”
Fatal error: Call to undefined function gravatar() in /homepages/2/d142238593/htdocs/baldpunk/wp-content/themes/Slurpie/comments.php on line 54

But why would I want to change it in the other php files if this works? Will there be a problem???

Because the featured post is actually still on the page. You’ve just hidden it in graphical browsers. Ideally, the theme templates need editing to remove the featured post completely – if only because it will reduce the page download time.

With regard to your Gravatar problem, the problem may lie in your theme or in your current settings within Admin/Settings/Discussion. What version of WordPress are you running (check the bottom right of any Admin page)?

The version is 2.7.

Thanks for all your help!!!

Try deactivating the Gravatar plugin and then navigating to Admin/Settings/Discussion and activating one of the default avatar types.

It didn’t work…

Thansk again.

Can you drop a copy of comments.php into the WordPress pastebin?

Did that do it?

I posted it twice. Sorry. It was my first time…

Its name is Bald P.

It was a problem at the host/server level. Their support people fixed it.