Forum Moderators: coopster
You could probably fix your scripts easily by using extract() at the top of all scripts that use the globals.
<?php
extract($_POST);
...
Then you can refer to them by their index name ($var)
I just had the reverse problem. I have always kept register_globals off, but recently uploaded something to a shared server that had registers_globals on. My app crashed. Why? Because in my mind (and by default in PHP), $_POST['id'] is not the same as $id. I mean $id is not the same as $ID, so it makes sense. But with register globals on, that is not respected.
Many people say that register_globals off is for security reasons, and it does provide a tiny bit more security. However, the reason they taught us to avoid globals back in my first programming courses (that was FORTRAN 77 folks), was not for security, but for code stability, maintainability and to make it easier to turn out stable code in a team environment.
So... that windy prelude leading up to this - turn register_globals off on your development platform and everywhere else you can, either in php.ini or in .htaccess (as I had to do on the shared server). Your programs will be more stable and maintainable in the long term. To me, the time savings from using globals is short sighted.
Tom