Months ago, I started a blog about interesting advertisements powered by Movable Type. During the installation and usage process, I got some knowledge about Movable Type, but the fact is that I’m still not quite familiar with it. Besides, the chosen topic is not quite related to my daily life. So now I’m stopping and deleting the blog.
Movable Type is a great blogging platform, and the team has been inventing many techniques and concepts, but the problem is that it’s defeated by WordPress because it’s not as simple and WordPress now has much more plugins.
The only advantage of using MT is that you don’t need to worry about the server load (digg effect, for example), but this is not a problem for us “little” bloggers. After several weeks, I even didn’t remember the url of the administration area.
I may start another blog, powered by WordPress, of course :)
Movable Type 4.1 was just announced. As stated in the blog post, this is a (the first?) stable release of Movable Type Open Source.
The download link given on movabletype.org is a zip file. However if you want gzip format, you can get it here. This version is under the GPL v2 license. And you can also download another version here if you agree to the personal license.
The two files are not identical, if you check them. That makes sense because they include different license agreements in their source code headers. However, they deliver the same code and functionalities as far as I know.
I just upgraded my Movable Type powered blog (not this one) to the latest version of MTOS and I really like the new layout of creating entries. Don’t forget overwriting the old mt-static directory – I missed this step as a novice and the admin page was messed up :)
Yes, I’m still a novice user of Movable Type. I’m very curious about a different approach than WordPress (OK, WP is a different approach than MT).
I followed the official instructions to install Movable Type 4 on this host, but the 500 error page appeared every time I clicked the “begin” button. Besides, the mt-check.cgi script generated an incomplete HTML output – it’s terminated at some point.
The log of the 500 error:
… Out of memory!, referer: http://example.com/cgi-bin/mt/mt-wizard.cgi
… Callback called exit at mt-wizard.cgi line 11., referer: http://example.com/cgi-bin/mt/mt-wizard.cgi
… END failed–call queue aborted at mt-wizard.cgi line 1., referer: http://example.com/cgi-bin/mt/mt-wizard.cgi
… Callback called exit at mt-wizard.cgi line 1., referer: http://example.com/cgi-bin/mt/mt-wizard.cgi
… BEGIN failed–compilation aborted at mt-wizard.cgi line 11., referer: http://example.com/cgi-bin/mt/mt-wizard.cgi
… Premature end of script headers: mt-wizard.cgi, referer: http://example.com/cgi-bin/mt/mt-wizard.cgi
I read through the troubleshooting doc of Movable Type but it seems not to be any of the problems listed there. When I searched for “Premature end of script headers: mt-wizard.cgi“, there’re no answers in English results.
I asked the support of this hosting company but at first they said it must be the problem of the script. Oh I’m using the stable release of MT4 and it’s used widely across the world. I wouldn’t believe it.
Then suddenly I received a message from root in the secure shell:
Please try to do your installation again.
We have identified a problem which has been corrected.
Yes, it worked like a charm. Soon I received a the problem description from support:
The problem appears to be related to memory limitation set in the apache configuration. This Apache limitation has been removed and memory is now controlled via PHP.
There’re quite a lot people stuck by this error when trying to start the Movable Type tour as I see. Most people don’t believe that the memory out error is true but indeed it is in my case. Hope this helps someone.