I have a similar problem Tom with a lot of the sites I work on. The ones i'm referring to are the ones on our shared servers. I can't turn debugging on at the server, unless everyone has overridden that in their pages, or else I only permit some ip addresses to see debugging. (that's not practical because people have different ip addresses all the time and we'd have to keep changing the list of ips) It's not really a simple answer to have debugging turned on for a shared server.
So I have debugging on at my dev server (my pcs) and in the rare event I need to see the debugging info on a live site - perhaps to fix a problem that hadnt shown itself in the dev environment - I'll beg and bribe the sysadmin to turn debugging on for my IP only for a short while as a temporary measure only. In general, unless there are really special reasons you should be doing all your debugging in your development environment (your own PC) where you can leave debugging on all the time, or turn it off, at your own whim. Cheers Mike Kear Windsor, NSW, Australia Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month On 7/4/05, Andrew Scott <[EMAIL PROTECTED]> wrote: > Tom, > > It sounds like to me that your staging (development) is the same machine as > your live server. This is really considered a bad idea, and should be 2 > separate machines. > > Anyway what you can do is tell the debugger to debug display by IP, thus > allows others not to see the debug except you or your developers. > > > Regards > Andrew Scott > Analyst Programmer > > CMS Transport Systems > Level 2/33 Bank Street > South Melbourne, Victoria, 3205 > > Phone: 03 9699 7988 - Fax: 03 9699 7976 > --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
