Why not: 1. place a .htaccess file in each existing client/developer directory switching the value to ON -- being careful to ensure you don't wipe over an existing .htaccess file!!
2. switch the value to OFF in php.ini This means all current clients will have continued support for ON, and all new ones will default to OFF. If existing clients which to go with OFF, they just delete the .htaccess file. OR the vice-versa can be done... advise clients that you are moving to OFF in a month, explain the benefits, and make a .htaccess file available to those who don't want to migrate... so that their stuff doesn't break. Most developers will know which way they're writing code. You ultimately need to: - change the default to OFF - allow existing clients to "patch" to ON Justin on 15/12/02 12:43 AM, Willem ([EMAIL PROTECTED]) wrote: > Hello, > > Lately we discovered that, by mistake, we've run PHP with register_globals > on for a few months for all our customers. > > Since we want to turn it off, we need to figure out which customers use the > 'register_globals' functionality so we can ask them to modify their scripts. > > However, checking all php code by hand is a non-trivial task, because there > are 20,000+ php scripts. Is there a way to: > > a) parse all .php scripts once and detect whether they depend on register > globals on? > > or probably easier: > > b) add something to our current setup so that when a scripts is executed and > uses the register globals functionality, we get a notification > automatically? > > Any suggestions? > Thanks! > > > Justin French -------------------- http://Indent.com.au Web Development & Graphic Design -------------------- -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
