After much agony and angst, it seems that the yesterday's upgrade of the Scienceblogs' site code was successful. Comments and blog entries are publishing as they should and with little wait time, so it appears that this was successful, thanks to the wonderful IT Systems consultant, who was hired to solve our problems! If you experience any problems, please do post about them here and be sure to tell me which browser you were using (we are noticing differences based on which browser and which browser version being used), the time (EDT) that it happened, what you were trying to do and what the outcome was (error message? if so, what did the error message say? or did you receive a time-out? or .. ?)
More like this
The advise I'm about to give you is something I've figured out my own and seems to work, but I do not know why, if it is necessary, or if there is a better way to manage this problem. If you have a better recommendation, please add it to the comments!
In June, I put up a post noting that open-source browsers accounted for
more than 50% of the hits at ScienceBlogs. At that time,
Firefox was 48.17%. Since then, Microsoft released IE7, which
includes a tabbed interface, and other enhancements that Firefox (and
Chrome Passes Firefox, Google May Pull Out Support: I stopped using Firefox around the 20th time it made me do something I shouldn't have had to do because it sucked as a browser. Firefox used to be my hero, now I regard it as somewhat dangerous, and I only use Google Chrome.
A lot of people (really, a lot—I've got a stack of emails on this subject) have been complaining that their browsers routinely crash on loading this site, and a few have been telling me about other peculiarities.
Seems to be working, I just commented on the cuckoo page. It chugs away for a while, but doesn't lead to the error page as it used to. Safari. rb