From 2b563d4fc879d18cde259fc3f06c32ed6f005425 Mon Sep 17 00:00:00 2001 From: Denis Flaven Date: Mon, 7 Jan 2019 16:24:31 +0100 Subject: [PATCH] Remove debug traces when updating objects A very verbose debug trace in the error log was happening each time a CmdbAbstractObject gets created non-interactively. --- core/inlineimage.class.inc.php | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/core/inlineimage.class.inc.php b/core/inlineimage.class.inc.php index da39298fb..73383be8a 100644 --- a/core/inlineimage.class.inc.php +++ b/core/inlineimage.class.inc.php @@ -178,18 +178,19 @@ class InlineImage extends DBObject $oInlineImage->DBUpdate(); } } - else - { - IssueLog::Error('InlineImage: Error during FinalizeInlineImages(), no transaction ID for object '.get_class($oObject).'#'.$oObject->GetKey().'.'); - - IssueLog::Error('|- Call stack:'); - $oException = new Exception(); - $sStackTrace = $oException->getTraceAsString(); - IssueLog::Error($sStackTrace); - - IssueLog::Error('|- POST vars:'); - IssueLog::Error(print_r($_POST, true)); - } +// For tracing issues with Inline Images... but beware not all updates are interactive, so this trace happens when creating objects non-interactively (REST, Synchro...) +// else +// { +// IssueLog::Error('InlineImage: Error during FinalizeInlineImages(), no transaction ID for object '.get_class($oObject).'#'.$oObject->GetKey().'.'); +// +// IssueLog::Error('|- Call stack:'); +// $oException = new Exception(); +// $sStackTrace = $oException->getTraceAsString(); +// IssueLog::Error($sStackTrace); +// +// IssueLog::Error('|- POST vars:'); +// IssueLog::Error(print_r($_POST, true)); +// } } /**