drchrisheard

Found the problem. Not a WordPress 2.7 issue at all, but an unclosed div tag. I don’t know why 2.5 didn’t choke on it.

moshu, that did not work for me, for some reason. I don’t know why.

However, I achieved the same effect by modifying a function in wp-includes/post.php as follows:

function get_the_title($id = 0) {
	$post = &get_post($id);

	$title = $post->post_title;
	if ( !empty($post->post_password) )
		$title = sprintf(__('Protected: %s'), $title);
	//else if ( 'private' == $post->post_status )
		//$title = sprintf(__('Private: %s'), $title);

	return $title;
}

The only thing I changed was adding comment slashes to the “else if” lines. However this affects private posts as well as private pages, and would have to be repeated upon upgrading, so it’s not a very good solution.

What if the theme does not have a functions.php page at all?

Argh.

I deleted the index.html file this morning.

I haven’t touched the blog since then.

Now it’s back.

Why is WordPress created this index.html and taking the blog out of service?

Thank you! I discovered the index.html file a few minutes after posting this. How did it get there? Was it perhaps created during my attempt (which failed) to import old Blogger items?

I’m having exactly the same problem.