Have you tried using the default template? I swear I mentioned this but looking back didn't see the post. What happens if you upload a blank search.php, that is with no code in it at all. Do you still get the 500 error?
Might be something worth looking into.
http://encodable.com/premature_end_of_script_headers/
Quote:
|
If your server is running the suEXEC security feature, you may get the "premature..." error, and it'll give you no indication whatsoever that suEXEC is the cause.
|
http://drupal.org/node/75265
Quote:
|
They told me that "the latest version of Drupal is unsupported so you are on your own" (in response to my telling them that their servers were causing 500 errors).
|
http://wordpress.org/support/topic/35294
Quote:
|
When I was with BlueHost, I had no Dashboard too. When I contacted their support, it was due to some feature that they had deactivated in PHP and they had no intentions of reactivating it for security concerns. It's nice to see that they are finally making considerations by willing to work with you on it, but that's long after I moved to Site5. I haven't had any Dashboard problems since.
|
Later in same thread:
Quote:
I officially heart Bluehost. They have fixed the problem (and quickly too!) It was less then 6 hours ago when I emailed them!
their response (short and sweet): "Try it now, it was our firewall causing the problem, I added the wordpress rss feeds to our
firewall trust list, and its coming up for me now."
|
I'm not knocking you or bluehost, but nobody I have heard of since August of 05 has brought this up as an issue. For it to be a problem with the script you'd think somebody somewhere would be experiencing the same problem. Granted you are using a less common template, hence my suggestion to revert to the default.
Support here is great, maybe you didn't get a reply as fast as you'd have liked, but you are getting help. Comments like these certainly won't encourage people to help you, as they are quite negative in tone:
Quote:
|
Latest error, help would be nice.......................
|
Quote:
|
I'm not throwing stones (like others)
|
Actually you might have pushed away one of the people most likely to solve your problem... He wasn't throwing stones, just making a statement that it isn't likely a script problem, and that often hosts push back support on the script without looking at their own stuff. It happens, look around the web, you will see this stated about various hosts all the time.
Quote:
|
If this is the service that a purchaser can expect, than others should know what to expect.
|
Quote:
Well, I'm not happy now , no help, problem not corrected. HOW ABOUT SOME HELP........................
|