MrPhil, on 13 April 2012, 14:00, said:
Wow. That's way overkill for a php.ini file. It looks like the host gave you a copy of their master php.ini file, which you normally don't have access to. [I would worry about your host's sense of security if they're going to give out potentially sensitive information like that, without requiring you to sign in blood that you won't make it public] All this information is probably available in the phpinfo() call, if you ever want to see its current state. Anyway, your php.ini needs only those settings that are different from the default (host php.ini). Just the stuff you've changed is needed.
There is no intersection that I can think of between php.ini and your configure.php settings.
If you've completely updated your osC code to PHP 5.3 level, register global variables should be off. Register_long array names appear to be already off. You may still need to explicity give date.timezone, to avoid warnings. There may be something you can do in there to turn magic quotes back on, for the time being, or else suppress "deprecated" function warnings.
There is no intersection that I can think of between php.ini and your configure.php settings.
If you've completely updated your osC code to PHP 5.3 level, register global variables should be off. Register_long array names appear to be already off. You may still need to explicity give date.timezone, to avoid warnings. There may be something you can do in there to turn magic quotes back on, for the time being, or else suppress "deprecated" function warnings.
Hi Phil,
Just wanted to say thanks for the push to upgrade OSC. I downloaded the latest version and in the extras dir there's a couple of upgrade pages. So far I've worked through the guide that updates MS2 to RC1, which took hours and was a bit tricky because I'm applying it to files that I've already modified for php 5.3 (e.g. the guide still uses $HTTP_GET_VARS etc).
The good news is that this first upgrade pass has solved the main issue (due to improved session handling methinks) but the bad news is that somewhere burried deep within the code it's trying to use http instead of httpS (the "shop" part of my site (i.e. OSC) runs every page using SSL) so there's more work to be done, but at least I can see light at the end of the tunnel.
Thanks






Find content
Male

