Or what I learned this last weekend?
[style=floatpicleft>Apparently.

As one small business supporting another small business, I understand. I finally broke down and called tech support Saturday morning, “they’re working in it,” was the recorded message.
I wandered up to the Pecan Street festival and had some “mystery meat on stick, probably fried, maybe baked, who knows?” kind of food. I pointedly ignored the problem.
Sunday morning, I tried a quick fix after I discovered that a half-dozen sites that I manage, or have access to, or whatever, on the same server, were all running just fine, albeit, without the interactive features I tend to employ. A simple script to echo the date and time could knock a page off-line, and with my site? The four most heavily trafficked pages, entry pages, all have a few bits and pieces of code that require interaction.
Date, time, content retrieval, and the rotating graphics, all of them are basically “moving parts” and the moving parts & pieces weren’t moving. Hence the whole thing was offline.
What I learned:
I tend to see the web page as a fairly static, text-based medium. But even employing a few moving parts, my page is far more active than I thought. It’s grown by accretion and influence rather than in a direct, lineal manner. But the highest traffic hits the most interactive of the pages. The more it wiggles, the more folks hit it. Wonder if that’s like fish, too?

(click to visit)