03-20-2008, 10:26 AM
I can take a look at it if nobody has fixed it as of yet. My main concern is that I don't have a testing ground that uses php5 which I'm assuming is what you upgraded to. Its much harder to just look at something and fix it than to be able to run tests and such on it. I'd be willing to give it a go though.
My first reaction is that it is a problem with register_globals. In php4 and under it was turned on by default and in php5 it is turned off (I just read that in php6 it is removed completely). What this means is that if you have a form field of name="image" and the script references the value with $image then it won't work. The correct way would be $_POST['image'] or $_GET['image'] depending on which way the form is set up (probably $_POST). It is more secure to be using $_POST and $_GET anyway so if this is the problem then it may be a good thing that it is being forced to be fixed.
I've also done a quick search and found a few sites refering to problems with $_POST after upgrading to php5. It seems to be an issue with mod_bandwidth and php5 interacting badly. Here are a couple of quotes.
Of course then I wonder why other scripts (like this forum) aren't having issues. The main site and the forum could be on seperate servers (obviously you would know this, I don't) or the forum script could just be well written enough to work around the issue somehow.
My bet though is that it is the register_globals issue.
My first reaction is that it is a problem with register_globals. In php4 and under it was turned on by default and in php5 it is turned off (I just read that in php6 it is removed completely). What this means is that if you have a form field of name="image" and the script references the value with $image then it won't work. The correct way would be $_POST['image'] or $_GET['image'] depending on which way the form is set up (probably $_POST). It is more secure to be using $_POST and $_GET anyway so if this is the problem then it may be a good thing that it is being forced to be fixed.
I've also done a quick search and found a few sites refering to problems with $_POST after upgrading to php5. It seems to be an issue with mod_bandwidth and php5 interacting badly. Here are a couple of quotes.
http://www.webhostingtalk.com/showthread.php?t=509419 Wrote:WN-Ali: I thought I should share the solution for this issue, it is caused by mod_bandwidth. Disabling mod_bandwidth will resolve the issue
ub3r: I actually ran into this problem back about a year ago. I think you can also move the module order around, in order to have php5 work alongside mod_bandwidth.
Scott.Mc: I had the same problem a few months back to, a work around is load PHP5 module before mod_bandwidth as php transmits the document without going through mod_bandwidth.
http://www.theblog.ca/php5-form-post Wrote:Eventually, the technical support guy switched off mod_bandwidth in the Apache configuration file and now everything works magically again PHP 5 it is!
I don’t really know what mod_bandwidth does (maybe it was actually a problem with memory limits?), but if you are having a similar problem, try looking there…
Of course then I wonder why other scripts (like this forum) aren't having issues. The main site and the forum could be on seperate servers (obviously you would know this, I don't) or the forum script could just be well written enough to work around the issue somehow.
My bet though is that it is the register_globals issue.