CMS Woes
June 4th, 2007My experience with the Charlottesville City School’s tech support has been anything but pleasant. I first ran into trouble with the school’s server system in Spring of last year, when I began to design the website for CHS’s Theatre Department. You see, I’d written this wonderful little Perl script to handle the image gallery. I mention it to CCS’s webmaster - “Oh, our server doesn’t support Perl.” Of course. It’s not like every web hosting company you come across these days supports it or anything…
So the website tumbles on for the next year or so, getting about 100 pageviews a day (heh, more than I can say for this blog, anyway…), generally working out. But the problem arises in finding a successor for next year, when I’m no longer around to manually edit the shtml. But lookie at what I’m using right now - a Content Management System. Perfect! Even my theatre teacher will be able to edit that after I’ve left the school. All I need now is a MySQL database.
Oh wait. The CCS server doesn’t support MySQL, either.
Apparently, I’m going to have to use the school’s CMS (Adobe’s Contribute) if I want to set one up on their server. Coranto won’t work either, because it requires Perl. Normally I wouldn’t complain about getting free Adobe software, but I’m not exactly in the mood to learn another new CMS at the moment. All I want is a MySQL database - is that so much to ask for?
