#2957 Fix, and remove, major debugging prints

[Jamie McCarthy]

Right now the API is set up to warn us about problems
when the code tries to access invalid skins. As a
result, each index.pl hit seems to drop about a dozen
lines in the apache error log like:

[Sun Jul 18 19:38:50 2004] [error]
:Slash::Apache:/usr/local/lib/perl/5.8.4/Slash/Apache.pm:333:determineCurrentSkin
called but no skin found (so using default) for
ellie.jamienet

[Sun Jul 18 19:49:28 2004] [error]
/index.pl:Apache::ROOTellie_2ejamienet::index_2epl:/usr/local/slash/site/ellie.jamienet/htdocs/index.pl:59:determineCurrentSkin
called but no skin found (so using default) for
ellie.jamienet

These are important, they are problems we should fix.

And this may help the site run faster; it can be
surprising how much a ton of debug prints will slow
requests down... if we can't immediately fix the
problems, we should remove the debug prints at least
for our production sites and try to solve the problem
on test sites...

[Tim Vroom]

Logged In: YES
user_id=596132

I'm not really seeing that high of a volume of these error
messages. Perhaps you already fixed something related.

The lines I do see seem to be originating from looking up
the skin based on an external ip, internal ip (probably
originating from monitoring), or legitimately incorrect
hostnames.

What might be useful is setting up a regex in a var which
turns off these warnings for certain hostnames/ips.