khairul neezam on February 14th, 2008


Disclaimer: Profainity.

The past THREE bloody hours, my domain was inaccesible. Anyone who tried accessing it was routed to an error 500 page. I got so damn bloody fed up trying to figure out the @^&#!* problem.

Thing is, my sub-domains work fine! So there had to be a problem with my main site.

Wordpress is fucking weird. Errors suddenly happen out of the blues. And I've no idea WHY at all. I mean do they like EVOLVE or something? Xmen issit?! Kan ni na.

This was the fucking error:

[error] [client 202.156.x.x] Premature end of script headers: /xxxx/xxxxx/public_html/index.php 

Good thing there was Google. Kan ni na. I really didn't understand how to solve the problem actually. I trial-ed and error-ed. 

The problem was with my index.php file, so I had to do something about that 5-lines of code. YES FIVE PATHETIC LINES. The 5 lines that's been giving me this fucking headache I have right now. AND I HAVEN'T HAD DINNER YET. 

I added this line within my php clause:

header('Content-type: text/html; charset=utf-8');

Then, I FTPed the updated file and reloaded my site. IT WORKED! Like damn cheebye. FINALLY.

^@%#$^!%$# you wordpress. Can you don't like suddenly decide to genetically evolve and ^%#Q@ me in the jubor? 

2 Responses to “Wordpress woes: Premature end of script headers”

  1. It isn’t WordPress because I did not encounter any errors. It is best to go right into the lines where the error is occurring. WordPress is possibly the best CMS on the web.

  2. looks like someone is having a bad day. Dun werry, programming can lead to this. Even small scale programming. One stupid letter missing, and the entire thing doesnt work.

Trackbacks/Pingbacks

Leave a Reply

You will be able to edit your comment after submitting.