If you have Javascript enabled and would like to view the lastest version of this Weblog, please go here.
June 24, 2004
Changing my religion...
And I’m not talking spirituality here, I’m talking blogging...
Go with me here…
Ok, so this is when I join the ranks of those who are abandoning MovableType for another weblogging system. But, I’m different… Really. I mean, I love MovableType. I am very happy with how it works as a weblogging tool (and I’ve checked out several — everything from homegrown, OpenSource apps to commercial suites that are slicker than snot. But, in most comparisons MovableType stands up to the best of ‘em. And I’m not even talking about v3.0, either — I’d be more than content to stick with v2.66, though if I were going to stick with MovableType, I would be happy to pay for a licence.
So, why am I switching then?
Well, partly because I’d like to be more in touch with OpenSource. In the past eight months or so, I’ve really started to appreciate what the OpenSource ideal has to offer. I’ve been reading a lot about it. I’ve been listening to a lot of people talk about it. More and more of the software that I use was made with the GNU GPL. So, I figured, if I’m switching to OpenSource for all of my desktop apps, I might as well switch my weblogging app too.
Ok, so I’m an idealist, but that’s only part of it.
The other reason I’m switching, is because MovableType and MySQL seem to have a few problems with my current webhost. You see, every time I create a new entry in MovableType (like this one here), I get a “HTTP 500 Internal Server Error” when I click the Save button — which basically just tells me that something went wrong. And, checking my raw access logs reveals nothing.
Anyway, this problem wouldn’t be so much of a problem if it only affected what I did here behind the scenes. But it doesn’t just affect me, it affects you also. This mainly manifests when you leave a comment (as you may have done in the past). Yep. Every now and again, that same old 500 error pops up, making you think that the comment didn’t take. But it did. Don’t worry. And because you think that the comment didn’t take, you try to leave the comment again. And again. And again. And this is frustrating!
I apologize for this.
My webhost seems to think that these issues are occurring because my MySQL database is getting too large. This is bogus. I have an alotted 100MB of MySQL space and even though this Weblog is now at 313 entries (including this one) and 486 comments — plus another couple of Weblogs that I host for other people — my MySQL database is still only around 6MB.
This all meaning that, try as I might, I cannot come up with a solution for the incompatibilities that exist here in my “virtual” environment…
So, if you’ve read this far, I bet your in utter suspense about what’s coming next: the weblogging tool that I have chosen to switch to!
Ahem… Well, I am in suspense anyway.
The tool of choice is going to be Pivot. I have talked about Pivot a few times before and I have used it for my Adkoc website and for my friends’ Rob & Erica’s Blog.
I like Pivot for a number of reasons. First, it is an OpenSource app (which I have already gone on about). Second, it is easy to install and easy to use (ok, this counts for reasons two and three). Last (for the sake of brevity), the user-base and support for Pivot is unmatchable — even by MovableType standards (which, I must add, now come at a price). Pivot is constantly evolving and the developers are always happy to take suggestions about how to make Pivot better.
I could go on about why I love Pivot (I’d be able to list multitudes more than just four short reasons), but I won’t. Let me just end by saying that the next Blog entry that you see here will not be a MovableType entry, but will be contined within the shell of something completely different.
Same bat channel. Same bat time.
(Oh, and, yeah, I have happily donated to Pivot!)
Posted at 2:02 pm
Trackback:Trackback Link:
