Today I join Thomas Arie Setiawan to dig into his Weblog's problem. I am curious because at the first I did with debugging, it is ended with error message Premature end of script headers. As far as I know from common Perl problem, it is about end-of-line difference between UNIX and Windows. So I made file type checking and ensuring that anything is in UNIX format.

Still that error message appears!

To make sure that there is no file with incorrect file format or permission, I unzip new MT tarball, and upload this new version into Thomas's directory both from my Linux and Windows boxes. Still misterious and error log from Apache does not tell much.

After 2 hours fixing and testing, I went into Google for "500 internal server error mt rebuild" but found nothing except there is one or two guys facing similiar problems but no solutions explained. One statement told that someone has been helped by MT support forum comunity, so — as I planned for the last searching — I looked into Support Forum.

I found Thomas had posted his problem there, but no solution yet. I searched more specific 500 Internal error issue and found a possibility from process mechanism used by MT for building pages.

Having tried to set EntriesPerRebuild into lower value (20 and 5), rebuilding Weblog still got failed. Sure I do not know the limitation from Thomas' hosting server about this process and its effect to how MT works. The best thing I can do is exporting Warnadunia's content into my computer — which does not have such kind limitations :-) — and testing it by rebuliding all.

Bla and bla... it works!
Ups, Thomas's prejudice about the possibility using better hosting service this morning sounds becoming necessity for his hundreds articles in his Weblog.

For me? It seems that if somedays in the future I have to move my stuff into commercial webhosting, I have to deal between cheapest and scalable enough. I remember one discussion thread in Warnadunia Forum telling why MT is less popular in Indonesia.

[Added on 22/01] Thomas tells that he tweaked ThrottleSeconds variable in mt.cfg and got better rebuilding. I will also try to apply Thomas' original layout into my trial in my computer.

Backup and backup!

Since today is one month after the last backup (10 Dec.), it seems one month regular backup is a well worth to be started. Our websites grow from static to database-minded with more configurations and pictures.

CD Rewritable will be a good solution, at least I can rotate the lattest 6 backups.

January 2004 — new year! — is marked by renewing my Weblogs' layout. Started before end of December for #direktif, I reconstructed its layout with inspiration from Six Apart's clean and smooth block. So I removed unnecessary entries inside sideblog and changed all bold-style anchor into normal, underlined font. Seems the nature and simple-easy Web page comes again. The red-white combination is, of course, still main color for #direktif with additional golden strip.

31 Dec. is the date for my last post in #direktif for 2003 and this is first entry for new layout.

New year comes and some days after I completed new design for Coret Moret. Similiar with #direktif for global layout, I focused my writing for all pages, so menu is only a sticky note placed in right part. Coret Moret's new design is inspired by this Writing in Silence's template. I also made space for Coret Moret narrower, compacted in the middle with smaller font was choosed. There are so many unnecessary things (mostly experiment part with MT) were removed. Only my articles exist — those are now the focus on my Weblog! I also made it last article is shown in complete form on main page; last articles were displayed fewer.

For these changes, I wrote their spirit, Tata Letak Baru (A New Layout) as first entry for year 2004.

Since 1 Dec, I pulled my tutorial out from Coret Moret to its own page, or die();. My primary consideration is they need to be arranged into its own more spesific categories, so it will be more flexible to be done in their own weblog. More than that, it is also — hopefully — easier for visitor who comes for that topic, get into suitable location.

Or die(); is a simple behind my mind: I just type my trick and very practical experience in front of computer, especially about configurations setting and programming. So it will be easier for me to repeat reading about some "mysterious" solutions that come incidentally, for example. And, if they are also useful for others, why not to be share?

Having seen an example from Budsz's MRTG, I think it is an interesting point to have this kind of system's report. Unpacking it from Debian's package, I setup MRTG's page and observing external connection's traffic.

Having had a dream for a long time, finally I purchased two web.id domain name for my weblogs. Coretmoret.web.id for Coret Moret and direktif.web.id for #direktif. To ease the process and also use their DNS for registering my computer's IP address, I choosed Murih.

Of course, from the old address, as subdomain of degromiest.nl, rewrite rules to a new address are provided.

<VirtualHost *>
ServerName coretmoret.degromiest.nl

RewriteRule ^/(.*)$ http://coretmoret.web.id/$1 [R,L]
</VirtualHost>

With generousity from CSS2, and also thank to Nimbus for suggestion, I replace Printed Version from my Coret Moret and #direktif. It is a simple step: all I have to do is providing stripped version from original, screen-oriented stylesheet. Because MT's default template consists of main block such as links for my sideblog and comments-head for commenting part, I can easily hide them in printer stylesheet,

.links, .comments-head { display: none; }

I provide printer feature only in Individual mode, so inside its template, I made this modification

<link rel="stylesheet" href="<$MTBlogURL$>css/styles-site.css" type="text/css"
media="screen" />
<link rel="stylesheet" href="<$MTBlogURL$>css/styles-printer.css" type="text/css"
media="print" />

The document has two separate stylesheets now, each for specific media.

This solution does not provide separate document for printer version, instead it gives proper view (guided by stylesheet) for printer. To see the result, and not by messing printer, Print Preview menu in browser can be used.

Finally, to provide link for visitor to print, JavaScript will help,

<a href="javascript:this.print()">Print this page</a>