Also it looks like the COOKIEHASH issue is a WPMU (multi user) thing and not a WP vanilla one. Are you using WPMU?
I need more coffee this week.
You’re going in through http://www.myurl.com/forums/bb-admin/content-forums.php Right?
It’s in a couple places
In the profile.php, obviously, there’s the bit for managing them. Also in topic.php there’s a lot of code checking to see it a topic is your favorite.
I suspect on topic.php you could comment out this:
<li<?php echo $class;?> id="favorite-toggle"><?php user_favorites_link(); ?></li>
And then on profile.php comment out this:
<p><?php printf(__('You can also <a href="%1$s">manage your favorites</a> and subscribe to your favorites’ <a href="%2$s"><abbr title="Really Simple Syndication">RSS</abbr> feed</a>.'), attribute_escape( get_favorites_link() ), attribute_escape( get_favorites_rss_link() )); ?></p>
That’s all theory, mind.
Hrm, did you have any problems before the cookie hash was fixed? I didn’t bother with it at all on alpha 2 and didn’t have any issues.
but in reality, administrators should be deleting the whole topic, not the only post in that topic. When you delete the only post of a topic, what are you expecting to be left over?
Yes, it’s a case of user-error finding a bug that should be caught. The code should say ‘hey, this is the only post, he must mean delete topic’ and move on, or the ‘delete post’ option shouldn’t even be there if it’s the only post in a topic. You’re both right 
Code should know better, user should read more (and FWIW, I made the same error when I was testing bbpress).
tdrinker, you can do all that in your templates. Either use CSS to make it invisible or remove it from your templates.
