I've looked into workarounds using third party feed services and calendar apps. Others smarter than me have stated that such measures "should" work; however, I lack the expertise to implement them from within the framework of a Webs template. Can Webs offer any engineering assistance in this regard?
Actually, now that I think about it:
Alternatives shouldn't have to be considered after 270 days. Right? Restoring a once-working feed shouldn't be the headache that Webs is making it. Right?
Again, I am not an expert on such matters; but, based on the W3C Validation Service results, the "fix" appears to be a matter of restoring field(s) or call-out(s) details that someone for some reason DELIBERATELY CHANGED at the beginning of May, 2011. Please, please, please just have someone check those connections...
And another thing:
"Once any new information has been provided to us, we'll be sure to provide an update here."
That's basically been stated a number of times over the past nine months. I do understand that this is standard operating procedure, Dom, and that all intentions are good; however, scroll back through this thread and its predecessor. In the last nine months, when has anyone ever posted an unapologetic, unprompted, honest-to-goodness update?
Actually, I'll save you some time - the answer is "never." If you still feel like scrolling, though, then pull up this Wikipedia reference
</somewhat snarky></somewhat serious>