This afternoon I have been a bit blue with bluehost. I have been ramping up for a project I will be working on over the next month, and I finally got motivated to install the Content Management Systems Drupal and Typo3 (I am going to try working through both to see which one is best for the project). When I opened the script installer Fantastico, to my great surprise, neither were available. I knew they had been previously available because I had installed both programs using Fantastico on Bluehost to play with these different systems a few months ago. So I called Bluehost and found out, with a bit of uncertainty on the tech’s part, that Drupal v.4.7.2 and Typo3 v.3.8 are for the moment -this is where the uncertainty manifested itself- unavailable through Fantastico because they have recently had problems with both applications. Hmmmm … problems? How do you call these problems?! (Excuse the Strong Badian moment.) I asked if they planned to resolve the issues and have these applications back up and running through Fantastico anytime soon? To that question I was told that the person who found the bugs with Typo3 was on break and that as of right now they could not support Drupal 4.7.2. Not very reassuring for those of us interersted in using CMSs through Bluehost.
After this I decided to use a Typo3 installation I had installed (using bluehost, mind you) for an entirely different set of sites I worked on previously as a temporary development space. And at this moment my surprise became something closer to concern. I was uploading some images when I began getting a 500 Internal Server Error message (see image below) that basically disabled all of the installs, i.e. blogs, wikis, lyceum, etc., on my web-hosting space. However, the various sites on my account were back up and running in a matter of a couple of minutes.
Click on image to see a larger copy of the error message