Last week, I managed to break my weblog. Today, another problem came on top of it. This problem appeared to be a lot more serious, and required a much more urgent fix.
The first problem appeared to be caused by an illegal name for one of my new templates. Sadly, Movable Type didn�t mention this restriction when I saved the file. However, when I�d try to access the templates index from that point forward, it would return the following:
maketext doesn't know how to say: ___ as needed at lib/MT.pm line 1120
Not being able to access the templates index wasn�t the only problem, though. Not even the most serious one. Automatic rebuilds for all weblogs on this install of Movable Type showed to be broken, and no new templates could be created.
Today, at work (internship at Vorm Vijf), I received a message from Casper via msn Messenger about my site being down. I didn�t believe it at first: after al, our server had been up and running for over 11 months (dispite some heavy conditions at times). (The up-time of the server had been oevr a year, by the way.)
Thus, I checked acjs.net in my browser, and indeed, no response. Somewhat confused, I tried to access some other sites that are hosted on the same server (Garret.tv, Fragile-Minds.com, etc.) � no response (not even a 404). When even ftp showed no sign of interaction, I started to panic a bit.
FatSatan (the guy that takes care of the payment of the server), had not showed up online for several months, and some question had risen among the people involved about whether he�d taken care of the server payment during this time. Hence, my reaction.
Luckaly, I remembered FatSatan�s log-in data to the account holder server management site. I was pleased to see payment was not the issue. However, it did not what the problem was, so I decided to reboot the box (for the first time). Mere minutes later, all sites were up and running smoothly again.
I fixed a problem in Houston with the click of a button in The Hague. Awesome.
Now, I was left with a broken weblog. I considered putting my own cms to effect, but considering it�s been in the planning phase for over a decade, and I�m an insane perfectionist on the matter, and I�m very busy with other things, I let that idea go rather quickly. Instead, I could use a fresh and clean install of Movable Type (opposed to the old version that was updated multiple times, during which process various external plug-ins had become absolete and/or broken).
So, yeah; this is the first post from the all new install (from a new cgi-bin sub-folder, which should/could slow down comment spam at least for a bit). Now I�m left with importing old entries (300+); creating new templates (I have some ideas it); and perhaps do some prosponed writing (which has become too much to actually catch up).
I�ll be at it, then.
ACJ3 comments so far.
Test.
Posted by: ACJ on February 18, 2005, at 21:58
The maketext error has to do with Locale::MakeText, which does the localization of strings in MT. (Type "man Locale::MakeText" to learn how it works.) It's used everywhere MovableType does an "$app->translate('blah')" (which is a lot of places). The translation tables are in lib/MT/L10N/ . You can probably work around the problem temporarily by specifying a translation for whatever the offending text is.
Posted by: Jacques Distler on February 25, 2005, at 05:29
Another test. Adopted your
Posted on March 5, 2005, at 23:27