Page 2 of 2

Posted: Tue Jan 04, 2005 9:59 am
by feyd
ask them to upgrade their php to a newer version, or change the php.ini for you. It can't hurt. :)

Posted: Tue Jan 04, 2005 10:59 am
by patrikG
[php_man]ini_set[/php_man]

Posted: Tue Jan 04, 2005 11:20 am
by feyd
wouldn't using ini_set be kinda pointless by that time? ;)

Posted: Tue Jan 04, 2005 11:25 am
by patrikG
there are many ways, ini_set is one, the user notes list a couple more. Why would it be to late?
php manual user notes ini_set wrote: There is another possibility by changing PHP Settings!
If your Webspace is able to handle ".htaccess" files, you're able to change PHP_INI Settings through this file!
To disable register_globals you have to set:
php_value register_globals 0
If you wanna set other settings, feel free, because there is no problem!
These Settings are set before running the script, e.g. the results of register_globals, when setting a parameter in the URL like 'foo.php?foo=stuff', is not present, $foo is unset.

Posted: Tue Jan 04, 2005 11:32 am
by feyd
because an ini_set would be inside the php script, by that point register_globals has already run its course. I'd say .htaccess would be the best route (if allowed/supported) and the provider doesn't want to change the setting internally.

Posted: Tue Jan 04, 2005 11:35 am
by patrikG
you are, quite arguably, though, right :)

Posted: Tue Jan 04, 2005 1:41 pm
by John Cartwright
look at the user comments in register globals section