title: Suppressing errors beyond setting ERROR_REPORTING ( display_errors perhaps? )
body: <p>Let's say I'm basically inheriting a <em>live</em> site that has a lot of errors in production, I'm basically doing a recode of this <em>entire</em> site which might take a month or so. </p>
  
  <p>There are some cases in which this site was reliant upon external xml file feeds which are no longer there, but the code wasn't properly setup to supply a nice clean error message ( there are various similar circumstances ) - the client is requesting that at least these error messages go away even if for example the content from the xml file isn't published so we wouldn't be seeing php errors and a blank region on the page ( so the rest of the page can look "fine" ).</p>
  
  <p>At one point I have heard of someone using set_error_handler to nullify some cases where it isn't <em>extreme</em> and I had the idea of setting it up to store error messages in a file/log or email them ( and try to not have duplicate error messages ) basically so end users don't have to see those ugly things. </p>
  
  <p>I'm looking for tips from anyone who's actually done this, so thanks in advance.</p>