Been taking a look at WordPress, and so far it looks good.  It'd also force me to learn PHP, which I've been meaning to do for quite some time now...

---
... or I could always not upgrade, but I'd like to get some of the features of MT3 (some of which are already available in other CMS's), and the great familiarity that would come with it.  Though, however, switching CMS's may not be bad, and besides, most of them out there can and will import MT entries.  Hm..  I'll have to look at WordPress a bit more.  I've already uploaded the zip file that contains everything to my site, just gotta unzip it (whatever happened to our telnet access?) and install.  Hm.  On the flip side, however, I would have to start EVERYTHING over again (site-wise, not entry-wise), I'd lose all my templates and such and would have to make new ones.  Actually...  I could still use my current ones, but they aren't PHP compatible, and if I am to switch to a new CMS that uses PHP, I'll wanna use PHP too, right?  Right.  Besides, a new layout would not be a bad idea, i'm still (technically) using the default one that came with MT.

ACK, the bell has rung, school is out.

Oh, within that last two weeks, I've gotten four spams from the following IPs:
205.215.195.253
200.49.218.125
141.83.165.100
203.59.246.76

Have fun, those oh you that know how to do stuff.

Check it out here.

This site gave me the basic layout to work from, and I've been modifying it as I please to get it to look like what I currently have.  However, if I do make this template my new main one...  I won't be able to use any of the other stylesheets that I've acquired through MovableStyle.  Hm, oh well...  We'll see how it works out.  If it doesn't look to good I won't use it, but will, instead, stick with the current layout.

I've also added a new plugin to MT.  It shows when a post was last updated.  If, and only if, a post has been updated, it will displayed "updated on $time" below the "posted at $time by $author".  Very cool.

Oh, one REALLY cool thing that Zempt allows for, is saving of entries.  So I can save an entry and finish it later, or if I want to start writing something (a poem?) I can save it and load it up later and proofread it or something.  Very cool indeed.

So, yea, that's pretty much all.

This is awesome.

After several e-mails back and forth with the Technolojik (our host) support guy, MovableType is working again!  It's so awesome!  Took me only 10 minutes at most to get all of my manual updates into MT and about 1 minute to rebuild the entire site (normally takes a bit longer, but I'm not complaining).  This is awesome!  It also means that comments are back, even for the updates that came while MT was down.  So, go ahead, comment.  I'm in a such a good mood right now!  =P

I am a co-owner of trashfolder.org, I am known as Satoshi. Our server went down about a week and a half ago, and the excuse we were given was "our harddrive crashed." OK, that's acceptable, happens to everyone. But then, we had no backups, and you're reply to this was "we don't keep backups." OK... Using an old backup that we had made (a month old, maybe), we got the site in working order again, only to find out that MovableType, our content managing system, didn't work. Why it didn't work, we didn't know. That is, until we carefully looked at the error message it was giving. It couldn't find two perl scripts. DB_File.pm and DBM.pm. Now, it worked perfectly before the crash, so that means these two perl scripts did exist on the server before it crashed. My question is, why don't these files still exist on the server? Why are they, all of a sudden, missing in action? Your reply, "oh, MovableType isn't compatible with cPanel." Excuse me, but it has never been compatible, and yet it DID work! Why was this? Because those perl scripts existed. Dioji and SniperX0, the other co-owners, have moved to another content managing system, called Pivot. Pivot isn't compatible with cPanel (I'm assuming that because it's not in the Fantastico options, neither was MovableType), but Pivot works perfectly. Just like MovableType, before the crash.

I'm not asking you guys to make MovableType to work again, because I can do that, given I have the required files (which did exist, so they should be back on the server). I'm telling (not asking) you guys to restore these files, DB_File.pm, DBM.pm, and any other perl scripts that were lost in the crash. As your customer, I expect you to restore the server to working order. "But the server IS working!" you say. I can't use MovableType because the server is missing some files, that is not working. Those files should have gone back up with everything else when the server was restored. "Oh, but MovableType isn't compatible with cPanel." It doesn't have to be, as long as the server has the required files (which you have, apparently, because they were on the server not too long ago) it doesn't matter. cPanel is NOT what the server runs on. The server runs on Linux. Just like my computer runs on Microsoft Windows. Just because cPanel is the admin software on the server, that doesn't mean that it IS the server. I run AOL Instant Messenger on my computer. Microsoft doesn't want me to do that, because it's not their instant messenging program. Microsoft doesn't want me running GAIM because it's a Linux program that has been ported to Windows. Microsoft doesn't want me to run OpenOffice because it's not Microsoft Office. Each and everyone of those programs works perfectly on Microsoft Windows. Microsoft can say whatever they want about incompatibility, but it won't change a thing, they still run, and are completely compatible. MovableType is compatible with Linux, that's all that matters. cPanel is just the admin frontend. Nothing more. I'm telling you, those perl files belong on this server, just as they were before the server crashed. If they do not get replaced, you're looking at losing another customer. "Oh, but you're only one of the three that own the domain" you say? We can switch providers. We have before. If the other two co-owners refuse to leave with me, it'll cost them more money, and they'll probably leave too. Think about it. Do you want to lose a customer just because you're too lazy to restore the server to how it was before it crashed? I'm not talking about all of the files we uploaded to the server, I'm just talking about the background stuff, the perl scripts, that kind of stuff.

Sincereley,
Satoshi