I think it is worth doing, as if we are making a site that can handle future events, we should be rendering the some of the other menu items dependent on availability due to date. If we are not making a site that can handle future events, then we are over-complicating the current site.

What you have said needs doesn't sound like it will be that much code, and doesn't look like as much effort as has already gone into other work done on the site. If you are adamant that this is too hard, let's merge this to get the integration of EventBrite, then address this particular issue separately.

As an aside, you don't need MVCContrib.TestHelper to unit test the views. I've tested controllers and views on the voting branch without it.