upgrade to 4.2.3 breaks html parsing as php

Forum Moderators: coopster

Message Too Old, No Replies

upgrade to 4.2.3 breaks html parsing as php

can anyone pinpoint why?

amznVibe

6:24 am on Aug 9, 2003 (gmt 0)

One of the sites we manage is hosted on a sever that was just upgraded to php 4.2.3 and immediately we lost html parsing as php, with a 500 internal server error...

removing the AddType application/x-httpd-php .php .php3 .phtml .html .htm
from HTACCESS file restores access to the site, but of course we lose all php commands on those pages...

they are taking forever to hunt down this problem, can anyone pinpoint it from a previous experience like this? I am guessing its a prior addhandler or addtype issues higher up in the httpd.conf?

(I tried playing with RemoveHandler and RemoveType to no avail)

Nick_W

6:40 am on Aug 9, 2003 (gmt 0)

Have you tried this?

<Files *>
ForceType application/x-httpd-php
</Files>

It might well be they upgraded Apache..?

Nick

amznVibe

6:50 am on Aug 9, 2003 (gmt 0)

I'll try that... apache was not upgraded, its still at 1.3.28

Nope doesn't change a thing, but thanks for trying...

jatar_k

7:56 am on Aug 9, 2003 (gmt 0)

the httpd.conf is messed, what they did, probably only they can fix. Sorry that doesn't help at all but it is probably the case.

amznVibe

9:28 am on Aug 9, 2003 (gmt 0)

Interestingly enough (just to follow this up) they claim that it wasn't the upgrade that broke it, but they had installed phpsuexec to supposedly "track down spammers on the server". They removed it and everything started working again. I am not familiar with this module so I am off to research it...

hpche

2:47 pm on Aug 9, 2003 (gmt 0)

This happened to me on my hosting company before. The main things I had to do to get it working again were to check all the file and folder permissions (it seemed if you've got them set too high it will cause a 500 server error - the apache error log is helpful if you've got access to it) and also to remove the php configuration directives from .htaccess (if you've got any there) and put them in a php.ini file in the directory instead. Good luck with it, I found it quite a pain to sort out but it was possible!

amznVibe

8:48 pm on Aug 9, 2003 (gmt 0)

I did one better, I got them to remove phpsuexec entirely. Back to normal, whew.

If you google for "phpsuexec" you'll notice dozens of horror stories as it breaks alot of PHP code. What's really stupid is that alot of hosts are installing this without prior warning to their existing customers and everyone wakes up the next day to find their site down or endless php error warnings.