In addition to the problem mentioned above with the fare calendar going completely blank if either the outbound or return trip is in May 2010, I'm getting a blank calendar for one specific route if either the outbound or return trip is in either October or November (2009). The blank dates have a "Selected fare is unavailable" hover message. Flights are actually available on those dates, the calendar is simply incorrect. It doesn't matter whether I start at the calendar entry page or go to the calendar after first looking at fares.

With probably over 4,000 possible routes to price, it seems unlikely I stumbled on one isolated case of this problem. Has anyone else seen it? I could run a script that would check them all so as to make a complete list of the problem city pairs, but I'll leave that to SWA. Even looking at one calendar per second it would take over an hour just to check every city pair.

One thing that is disheartening about all this is that if SWA had done a proper public beta before deciding the revamped site was ready for gated rollout, we could be posting enthusiastic encouraging comments instead of angry comments. Rather than being negative we'd be saying things like "this redesign has a lot of potential; it should be a very nice site when you finish working out the kinks." OAKman nailed it way back on August 15 when he said "In my opinion, the new interface is not ready for primetime and Southwest should address the problems before continuing to roll it out."